-
Notifications
You must be signed in to change notification settings - Fork 20
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
Chat download finishes, but does not progress to convert #415
Comments
This also occurred on my local instance for the same stream in the same way
|
Looks like it failed moving, the debug message before it, is just saying that it is about to move, but errors right after as the file is not found. If you exec into the API container, does |
I didn't tune in on twitch itself so can't say, this is the first time I've seen a stream of theirs. There was no live-chat.json in the tmp folder for either instance. Certainly possible there were no chat messages. |
Is there a VOD you can check if there were any chat messages? The chat-downloader tool doesn't create the json file unless there is a message so it likely could be this. I'll update the task to check if the file exists before attempting to move, and set the vod to have no chat. |
There isn't a VOD for this specific stream, but they do have other older VODs which do have chat. I think it's safe to assume in this case there weren't any chat messages. Hard to say since chat-downloader doesn't log anything. |
The logs say it did kill the process ID of the chat-downloader, so it didn't error out. Very likely just no messages. You can confirm nothing weird is going on with the channel by running |
Tested, seems to work fine with the channel in question, so yep just very likely there were no messages. |
First time I've seen this one happen.
Most relevant lines:
State it ends up in:
The
error opening file: open /tmp/41261224199_752758d6-06b9-11ef-be89-0242ac120009-live-chat.json: no such file or directory
is quite suspicious here, not sure why it would be trying to open that tmp file again, right after it has moved it to the vods directory.Full log for this VOD:
The text was updated successfully, but these errors were encountered: