FA-27812 / HTTP ranges / Member archive
An object store maps upload part numbers and byte ranges onto stored parts: a part begins at the sum of all earlier part sizes · case 02
An object store maps upload part numbers and byte ranges onto stored parts: a part begins at the sum of all earlier part sizes.
Case contract
x has stored part sizes in order and a query. ["part",n] (1-based) returns [206,bytes a-b/total] for that part, or [416,bytes */total] when n is outside 1..count or the part is empty. ["range",a,b] with inclusive bounds returns [416,bytes */total] unless 0<=a<=b<total; otherwise [206,rows] where each intersecting nonempty part yields [part-number,offset-within-part,count] in part order.
Why this case matters
Range responses combine representation identity, conditional requests, framing, and partial-object state.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| part-prefix-offset fixture 0 | [206, "bytes 8-10/12"] | [206, "bytes 5-7/12"] | Failed |
MEMBER ARCHIVE
The complete case is available to members.
This record includes three runnable implementations, regression fixtures, execution results, and source hashes.
Member access is invitation-based. Sign in with your invited account to inspect the sources.
Sign in to the archive ↗