FA-27418 / HTTP ranges / Member archive

An upload status endpoint reports committed byte coverage: extending a run changes its end while retaining its initial byte · case 03

An upload status endpoint reports committed byte coverage: extending a run changes its end while retaining its initial byte.

Member previewVariant 3 · 3 implementations · 9 checks per implementation

Case contract

x has a nonnegative complete length and committed byte offsets, which may repeat or arrive unordered. Reject offsets outside the representation. Return [complete|partial,acknowledged-range-field-or-null,next-missing-prefix-offset]. The local acknowledged field uses bytes= followed by comma-separated inclusive runs. Empty coverage has null header; an empty representation is complete. next-missing is the end of the committed contiguous prefix, not the highest written offset.

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
run-tail-update fixture 0	`["partial", "bytes=1-1,5-5", 2]`	`["partial", "bytes=0-1,4-5", 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.