Repository navigation
fix: report what the platform actually answered instead of a missing video - #4
Merged
juliantellez merged 7 commits intoSep 2, 2026
Merged
Conversation
…ing it a missing video
This was referenced Sep 1, 2026
This was referenced Sep 1, 2026
juliantellez
deleted the
diagnose-the-boundary-and-report-the-real-cause
branch
September 2, 2026 09:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What. The deployed page reported a working video as deleted. This makes the boundary say what the platform actually answered, then gives each cause its own page, its own status code and its own line in the log.
Why. The reader threw the same error whenever the title came back null, so a refusal, a rate limit and a genuinely missing video all reached the reader as one 404 saying "No video with that id". Nothing was logged at that boundary, so the log said nothing either.
The cause, from the deployed function's own log.
cause: bot_check, status 200, 1,412,860 bytes,has_caption_tracks: false,playability: LOGIN_REQUIRED, reason "Sign in to confirm you’re not a bot". The platform refuses the address the function calls from, and it refuses at the watch page, before the proof of origin work is reached. The same video read from a laptop returns 560 segments.Only a missing video answers 404 now. A refusal answers 502, says the video is fine, and offers the video on the platform. The deploy check stays red while the product cannot read a transcript, and it now names the cause instead of printing a bare 404.