FAILURE MAP
← Case archive

FA-26578 / HTTP ranges / Member archive

Repeated close events release a range handle only once · case 03

Repeated close events release a range handle only once.

Member previewVariant 3 · 3 implementations · 6 checks per implementation

Case contract

Events are close or tick. Initially one handle is open. Return [release-count,open]; subsequent close is a no-op.

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
stream-close-idempotency fixture 0[4, false][1, 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.

Sign in to the archive ↗