FAILURE MAP
← Case archive

FA-26918 / HTTP ranges / Member archive

A packed-object origin maps logical byte requests to immutable backing objects: zero-length map entries do not dereference backing handles · case 03

A packed-object origin maps logical byte requests to immutable backing objects: zero-length map entries do not dereference backing handles.

Member previewVariant 3 · 3 implementations · 12 checks per implementation

Case contract

x has pack strings keyed by handle, extent rows [logical-start,handle,physical-start,count], and explicit requested logical offsets. Extents may arrive unordered. Empty extents ignored. Reject negative mapping coordinates, missing handles, out-of-pack spans, or overlapping logical ownership. Return requested characters in request order, retaining repeated requested offsets; unavailable requested offsets yield None. This is a bounded storage adapter underlying HTTP range delivery, not interval normalization.

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
empty-extent fixture 4null"a"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 ↗