-
Notifications
You must be signed in to change notification settings - Fork 19
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
Json parsing crash in get_segments_internal #37
Comments
Maybe the API have changed. I will look at it, thanks for the report. |
Hmm I can't reproduce it. I added some logging and published new images, if it happens again please comment again with the logs. At least now if this happens it will retry to download segments. |
Will try that thanks. I had tried to log the payload but the last payload
was 404 and more than 30 seconds prior so it might not have been it. It
might just be an intermittent issue with the api but hopefully we'll find
out.
…On Mon, Nov 29, 2021, 7:35 AM Alexandre Morignot ***@***.***> wrote:
Hmm I can't reproduce it. I added some logging and published new images,
if it happens again please comment again with the logs.
At least now if this happens it will retry to download segments.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAHPXG4WRX6OGZOZFYACSV3UONXRDANCNFSM5I4SDSNQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Here is the debug log:
The video ID is CaLOiGEDPJQ which is 404, and trying again with the same video it's fine. Maybe something weird happens occasionally with the API on videos without segments... Here's another one, looks like it's different junk each time (this time with a backtick so I block quoted it)
|
Wow, I didn't expect that 😮 I will try to look at it by the end of the week. |
the response for skipSegments has changed but I don't think it should invalidate any JSON schemas |
Those new fields should just be ignored. |
Here's a new crash on my long-running castblock, running commit 243e756 , it seems to be related to the json parsing in https://github.com/erdnaxeli/castblock/blob/main/src/sponsorblock.cr#L49
The text was updated successfully, but these errors were encountered: