FA-27833 / HTTP ranges / Member archive

An object store maps upload part numbers and byte ranges onto stored parts: intersection offsets are relative to the containing part · case 03

An object store maps upload part numbers and byte ranges onto stored parts: intersection offsets are relative to the containing part.

Member previewVariant 3 · 3 implementations · 14 checks per implementation

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 fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
part-relative-offset fixture 6	`[206, [[1, 3, 2], [2, 5, 3], [3, 8, 2]]]`	`[206, [[1, 3, 2], [2, 0, 3], [3, 0, 2]]]`	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.