Skip to content

Fix GCS error handling for bounded artifact reads - #1020

Merged
ajroetker merged 1 commit into
mainfrom
fix/pr1019-gcs-error-envelopes
Oct 8, 2026
Merged

ajroetker merged 1 commit into
mainfrom
fix/pr1019-gcs-error-envelopes

Conversation

@ajroetker

Copy link
Copy Markdown
Contributor

Small immutable artifact GETs cap successful response bodies at the expected artifact size. GCS previously applied that same cap to HTTP error envelopes, turning missing, denied, or unavailable objects into ResponseTooLarge and then an artifact integrity error.

Give GCS a separate 4 KiB error-response allowance while preserving the successful response ceiling. Add a real HTTP regression covering 404, 403, and 503 responses, oversized error envelopes, and oversized successful bodies.

Validation: Zig 0.17 objectstore unit suite passed (cloud integration tests remain opt-in). The new regression fails without the fix with expected error.FileNotFound, found error.ResponseTooLarge. git diff --check passed.

Follow-up to #1019.

@ajroetker
ajroetker merged commit d2e9138 into main Oct 8, 2026
3 of 5 checks passed
@ajroetker
ajroetker deleted the fix/pr1019-gcs-error-envelopes branch October 8, 2026 15:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant