fix: normalize Cloudflare R2 range metadata - #279
Merged
Conversation
Use numeric property guards for the runtime R2 range shape. Cloudflare includes optional keys with undefined values, so structural union checks cannot safely discriminate suffix and offset ranges.
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
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
1 participant
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.
Summary
undefinedvaluesContent-Rangeoffsets while retaining zero-copy R2 streamingRoot cause
The deployed runtime returned an offset range object that also contained an undefined
suffixkey. The TypeScript union suggests those shapes are exclusive, but anincheck is not a valid runtime discriminator for this platform object. A production byte-range probe exposedContent-Range: bytes NaN-....Verification
206,Content-Range: bytes 0-1023/880729, and a 1,024-byte body