Repository navigation
Parse HTTP errors before writing media downloads - #174
Merged
omarryhan merged 3 commits intoNov 1, 2026
Merged
Conversation
Owner
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.
Fixes #120. Failed media downloads currently write the API error into the destination file or pipe, potentially overwriting an existing file. This change parses HTTP errors before the download writer runs, preserving the destination and the API's error details.
All 16 localhost HTTP regression/control tests pass after the fix; 14 fail on unchanged upstream. The broader selected suite passes 96 tests, including those 16. Another 96 API-definition tests pass. This is not a full-suite or authenticated Google test. No existing tests were changed.
AI-assisted implementation and testing.