FAILURE MAP
← Case archive

FA-26958 / HTTP ranges / Member archive

Partial cache admission publishes complete requested fragments atomically: a contradicting duplicate fragment invalidates admission · case 03

Partial cache admission publishes complete requested fragments atomically: a contradicting duplicate fragment invalidates admission.

Member previewVariant 3 · 3 implementations · 9 checks per implementation

Case contract

x is [old-visible-cells,events]. Events begin(id,expected-offsets), put(id,offset,char), commit(id), abort(id), read. One transaction at a time; unknown or mismatching ids ignored. A conflicting duplicate byte invalidates the active transaction. Commit succeeds only when every expected cell is present and replaces the old generation. Readers see committed cells sorted by offset. Return [read-snapshots,final-cells,pending-id].

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 fixtureActualExpectedOutcome
duplicate-conflict fixture 4[[], [[0, "a"]], null][[], [], null]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 ↗