Open user68329 opened 1 year ago
Debug mode adds following to the end:
127.0.0.1 - - [05/May/2023 08:20:00] "GET /?__debugger__=yes&cmd=resource&f=debugger.js HTTP/1.1" 200 -
INFO:werkzeug:127.0.0.1 - - [05/May/2023 08:20:00] "GET /?__debugger__=yes&cmd=resource&f=debugger.js HTTP/1.1" 200 -
127.0.0.1 - - [05/May/2023 08:20:00] "GET /?__debugger__=yes&cmd=resource&f=style.css HTTP/1.1" 200 -
INFO:werkzeug:127.0.0.1 - - [05/May/2023 08:20:00] "GET /?__debugger__=yes&cmd=resource&f=style.css HTTP/1.1" 200 -
127.0.0.1 - - [05/May/2023 08:20:00] "GET /?__debugger__=yes&cmd=resource&f=style.css HTTP/1.1" 304 -
INFO:werkzeug:127.0.0.1 - - [05/May/2023 08:20:00] "GET /?__debugger__=yes&cmd=resource&f=style.css HTTP/1.1" 304 -
127.0.0.1 - - [05/May/2023 08:20:00] "GET /?__debugger__=yes&cmd=resource&f=debugger.js HTTP/1.1" 304 -
INFO:werkzeug:127.0.0.1 - - [05/May/2023 08:20:00] "GET /?__debugger__=yes&cmd=resource&f=debugger.js HTTP/1.1" 304 -
127.0.0.1 - - [05/May/2023 08:20:00] "GET /?__debugger__=yes&cmd=resource&f=console.png HTTP/1.1" 200 -
INFO:werkzeug:127.0.0.1 - - [05/May/2023 08:20:00] "GET /?__debugger__=yes&cmd=resource&f=console.png HTTP/1.1" 200 -
127.0.0.1 - - [05/May/2023 08:20:00] "GET /?__debugger__=yes&cmd=resource&f=console.png HTTP/1.1" 304 -
INFO:werkzeug:127.0.0.1 - - [05/May/2023 08:20:00] "GET /?__debugger__=yes&cmd=resource&f=console.png HTTP/1.1" 304 -
127.0.0.1 - - [05/May/2023 08:20:00] "GET /?__debugger__=yes&cmd=resource&f=console.png HTTP/1.1" 304 -
INFO:werkzeug:127.0.0.1 - - [05/May/2023 08:20:00] "GET /?__debugger__=yes&cmd=resource&f=console.png HTTP/1.1" 304 -
Just started having the same issue, not sure what is causing the problem. Happening on fresh installation of Python and slack-export-viewer as well.
@user68329 Try two things:
slack-export-viewer --port 3000 -z /path/to/export/zip
Neither of these worked for me. To make it work, I have had success removing a lot of channels from the exported zip file from Slack, re-zipping it, then loading Slack Export Viewer. I have not determined a pattern as to how many channels works properly. Also, could be an issue with amount of lines of conversation in any given channel, or perhaps character issue/limit?
The clue is in KeyError: 'ts'
The issue is happening because it was expecting to find a time stamp in a message, but was unable to find it. Slack uses time stamps for Threads, so its likely caused by that.
The code in question is: tsepoch = float(self._message["ts"].split(".")[0])
Possible Solution:
if "ts" in self._message:
tsepoch = float(self._message["ts"].split(".")[0])
else:
tsepoch = None # Or any suitable default value
I fixed it by replacing the code at line 48 in message.py with:
@property
def time(self):
# Check if 'ts' key exists in the dictionary
if "ts" in self._message:
# Handle this: "ts": "1456427378.000002"
tsepoch = float(self._message["ts"].split(".")[0])
return str(datetime.datetime.fromtimestamp(tsepoch)).split('.')[0]
else:
return None # or return a suitable default value
this works as a workaround for now
Thanks to @MuratDoganer, I may have a theory on what's causing this. We have retention settings(message history to disappear after certain number of days) set on certain channels and all DMs. It's possible that because of this, the structure of export doesn't meet SlackViewer's expectations and yes, the possible solution above may fix the issue.
We also use Slack Connect with external workspaces and I've seen internal messages disappear because of retention settings, but external message stay within the same channel. This could be the culprit.
I see, it could be the cause! We use the default message retention values from Slack but was getting this issue on every export, decided to sit down and fix it today :)
I would put in a PR but seems like I cant at the moment
As soon as the app loads, i'm getting the below message. The browser shows "Internal Server Error"
Any idea what this could be caused by?
Tried 24-hour export and still the same issue.
Thanks