FA-27187 / HTTP ranges / Member archive

A multipart sender resumes framing and payload segments across transport credit windows: zero-byte windows remain visible to the transport caller · case 02

A multipart sender resumes framing and payload segments across transport credit windows: zero-byte windows remain visible to the transport caller.

Member previewVariant 2 · 3 implementations · 7 checks per implementation

Case contract

x has nonempty ASCII segments representing alternating boundary/header/body/framing bytes, and nonnegative write budgets. Drain in order, consuming each budget across segment boundaries. Return [one emitted string per budget,segment-index,intra-segment-offset]. Empty segments are skipped even with zero budget. A exhausted plan is stable. These preframed segments isolate cursor management from wire-format construction.

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
window-retention fixture 1	`[["A", "B", "C"], 2, 0]`	`[["A", "", "B", "C", ""], 2, 0]`	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.