-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implementing support for exporting threads #3
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Andrew V. Jones <[email protected]>
Just got this message, any clues? Successfully authenticated for team ******* and user ***** Thank you |
@filipedematos: you get this error if the "bot" you've created to get access to the channel does not have enough access permissions to read what you're trying to export. |
I'm trying to export my channels but the script keeps trying to fetch the first channel forever, irrespective of which channel (public or private) I choose. .............................................................................................................................................................................. .............................................................................................................................................................................. .............................................................................................................................................................................. .............................................................................................................................................................................. .............................................................................................................................................................................. .............................................................................................................................................................................. .............................................................................................................................................................................. .............................................................................................................................................................................. " |
Why do you think it is not still running? This export is extremely slow because Slack heavily rate-limits connections. |
Because when using https://github.com/lumbric/slack-export/tree/working-draft the job is done in less than 5 minutes (yes, without threads), whereas this script has now been running for 2 hours and is apparently still working on the first (public) channel, which contains barely any messages. And it has not written any data during those 2 hours expect at the beginning, when the channels.json, dms.json, groups.json, mpims.json and users.json files were created. The what_is_slack directory is still empty. |
Are you getting "fresh dots"? I no longer have access to a Slack instance to heavily test this with (which is why I wrote it).
These don't get updated when dumping threads; you get separate json files for each date (and in each channel). I can't remember if they're written as dumping happens or at the end.
I left this running over a whole weekend to dump a "small" channel. The rate limits on Slack are something like 10 messages (or maybe 100) every 1 second -- it really takes a long time to dump this way. If you care, before this line: add a |
After running for about 20 hours, the script breaks: During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
¯\(ツ)/¯ you're welcome to dive into the code |
Hi,
This PR adds support for dumping threads (in the regular Slack format) from channels.
Please see here for some more background: zach-snell#40
Cheers,
Andrew
Signed-off-by: Andrew V. Jones [email protected]