FA-27518 / HTTP ranges / Member archive

A zero-copy range sender accounts for partial progress reported with syscall errors: fatal errors remain terminal even after their last accepted bytes · case 03

A zero-copy range sender accounts for partial progress reported with syscall errors: fatal errors remain terminal even after their last accepted bytes.

Member previewVariant 3 · 3 implementations · 8 checks per implementation

Case contract

x contains absolute offset, remaining promised bytes, and syscall events [accepted,error], where error is none,again,interrupt,fatal. Counts outside0..remaining abort without advancing. Valid accepted bytes advance even when again or interrupt accompanies them. Fatal errors abort; zero remaining completes; again blocks; interrupt reschedules; zero bytes with none truncates. Terminal states ignore later events. Return state snapshots [offset,remaining,state,handle-open] after each event.

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
fatal-after-progress fixture 2	`[[1, 1, "running", true], [2, 0, "complete", false]]`	`[[1, 1, "aborted", false], [1, 1, "aborted", false]]`	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.