Understand the failure.
Verify the repair.
Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.
Explore the cases ↓How results are verified ↗WHAT THE ARCHIVE CONTAINS
100840 executable cases. 20168 are open.
Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.
The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗
A RECORD OF WHAT WENT WRONG
Browse the archive / 100840
Known complete length must extend beyond every returned endpoint · case 01
Known complete length must extend beyond every returned endpoint.
Known complete length must extend beyond every returned endpoint · case 02
Known complete length must extend beyond every returned endpoint.
Known complete length must extend beyond every returned endpoint · case 03
Known complete length must extend beyond every returned endpoint.
Known complete length must extend beyond every returned endpoint · case 04
Known complete length must extend beyond every returned endpoint.
Known complete length must extend beyond every returned endpoint · case 05
Known complete length must extend beyond every returned endpoint.
Content-Range metadata is retained only for partial or unsatisfied responses · case 01
Content-Range metadata is retained only for partial or unsatisfied responses.
Content-Range metadata is retained only for partial or unsatisfied responses · case 02
Content-Range metadata is retained only for partial or unsatisfied responses.
Content-Range metadata is retained only for partial or unsatisfied responses · case 03
Content-Range metadata is retained only for partial or unsatisfied responses.
Content-Range metadata is retained only for partial or unsatisfied responses · case 04
Content-Range metadata is retained only for partial or unsatisfied responses.
Content-Range metadata is retained only for partial or unsatisfied responses · case 05
Content-Range metadata is retained only for partial or unsatisfied responses.
Non-ASCII response bodies report UTF-8 byte length instead of character count · case 01
Non-ASCII response bodies report UTF-8 byte length instead of character count.
Non-ASCII response bodies report UTF-8 byte length instead of character count · case 02
Non-ASCII response bodies report UTF-8 byte length instead of character count.
Non-ASCII response bodies report UTF-8 byte length instead of character count · case 03
Non-ASCII response bodies report UTF-8 byte length instead of character count.
Non-ASCII response bodies report UTF-8 byte length instead of character count · case 04
Non-ASCII response bodies report UTF-8 byte length instead of character count.
Non-ASCII response bodies report UTF-8 byte length instead of character count · case 05
Non-ASCII response bodies report UTF-8 byte length instead of character count.
Chunked transfer coding removes fixed body length metadata · case 01
Chunked transfer coding removes fixed body length metadata.
Chunked transfer coding removes fixed body length metadata · case 02
Chunked transfer coding removes fixed body length metadata.
Chunked transfer coding removes fixed body length metadata · case 03
Chunked transfer coding removes fixed body length metadata.
Chunked transfer coding removes fixed body length metadata · case 04
Chunked transfer coding removes fixed body length metadata.
Chunked transfer coding removes fixed body length metadata · case 05
Chunked transfer coding removes fixed body length metadata.
Conflicting duplicate Content-Range fields cannot choose an arbitrary winner · case 01
Conflicting duplicate Content-Range fields cannot choose an arbitrary winner.
Conflicting duplicate Content-Range fields cannot choose an arbitrary winner · case 02
Conflicting duplicate Content-Range fields cannot choose an arbitrary winner.
Conflicting duplicate Content-Range fields cannot choose an arbitrary winner · case 03
Conflicting duplicate Content-Range fields cannot choose an arbitrary winner.
Conflicting duplicate Content-Range fields cannot choose an arbitrary winner · case 04
Conflicting duplicate Content-Range fields cannot choose an arbitrary winner.
Conflicting duplicate Content-Range fields cannot choose an arbitrary winner · case 05
Conflicting duplicate Content-Range fields cannot choose an arbitrary winner.
A byte-range client rejects partial metadata in a different unit · case 01
A byte-range client rejects partial metadata in a different unit.
A byte-range client rejects partial metadata in a different unit · case 02
A byte-range client rejects partial metadata in a different unit.
A byte-range client rejects partial metadata in a different unit · case 03
A byte-range client rejects partial metadata in a different unit.
A byte-range client rejects partial metadata in a different unit · case 04
A byte-range client rejects partial metadata in a different unit.
A byte-range client rejects partial metadata in a different unit · case 05
A byte-range client rejects partial metadata in a different unit.
A response digest describes the transferred slice instead of the whole object · case 01
A response digest describes the transferred slice instead of the whole object.
A response digest describes the transferred slice instead of the whole object · case 02
A response digest describes the transferred slice instead of the whole object.
A response digest describes the transferred slice instead of the whole object · case 03
A response digest describes the transferred slice instead of the whole object.
A response digest describes the transferred slice instead of the whole object · case 04
A response digest describes the transferred slice instead of the whole object.
A response digest describes the transferred slice instead of the whole object · case 05
A response digest describes the transferred slice instead of the whole object.
The representation length header does not collapse to the transferred fragment length · case 01
The representation length header does not collapse to the transferred fragment length.
The representation length header does not collapse to the transferred fragment length · case 02
The representation length header does not collapse to the transferred fragment length.
The representation length header does not collapse to the transferred fragment length · case 03
The representation length header does not collapse to the transferred fragment length.
The representation length header does not collapse to the transferred fragment length · case 04
The representation length header does not collapse to the transferred fragment length.
The representation length header does not collapse to the transferred fragment length · case 05
The representation length header does not collapse to the transferred fragment length.
A full fallback response replaces an existing download prefix · case 01
A full fallback response replaces an existing download prefix.
A full fallback response replaces an existing download prefix · case 02
A full fallback response replaces an existing download prefix.
A full fallback response replaces an existing download prefix · case 03
A full fallback response replaces an existing download prefix.
A full fallback response replaces an existing download prefix · case 04
A full fallback response replaces an existing download prefix.
A full fallback response replaces an existing download prefix · case 05
A full fallback response replaces an existing download prefix.
A continuation response must start at the saved prefix boundary · case 01
A continuation response must start at the saved prefix boundary.
A continuation response must start at the saved prefix boundary · case 02
A continuation response must start at the saved prefix boundary.
A continuation response must start at the saved prefix boundary · case 03
A continuation response must start at the saved prefix boundary.
A continuation response must start at the saved prefix boundary · case 04
A continuation response must start at the saved prefix boundary.
A continuation response must start at the saved prefix boundary · case 05
A continuation response must start at the saved prefix boundary.
Missing response validators cannot silently preserve a saved validator · case 01
Missing response validators cannot silently preserve a saved validator.
Missing response validators cannot silently preserve a saved validator · case 02
Missing response validators cannot silently preserve a saved validator.
Missing response validators cannot silently preserve a saved validator · case 03
Missing response validators cannot silently preserve a saved validator.
Missing response validators cannot silently preserve a saved validator · case 04
Missing response validators cannot silently preserve a saved validator.
Missing response validators cannot silently preserve a saved validator · case 05
Missing response validators cannot silently preserve a saved validator.
An unsatisfied continuation proves completion only against equal known total length · case 01
An unsatisfied continuation proves completion only against equal known total length.
An unsatisfied continuation proves completion only against equal known total length · case 02
An unsatisfied continuation proves completion only against equal known total length.
An unsatisfied continuation proves completion only against equal known total length · case 03
An unsatisfied continuation proves completion only against equal known total length.
An unsatisfied continuation proves completion only against equal known total length · case 04
An unsatisfied continuation proves completion only against equal known total length.
An unsatisfied continuation proves completion only against equal known total length · case 05
An unsatisfied continuation proves completion only against equal known total length.
Out-of-order downloaded ranges write at their absolute positions · case 01
Out-of-order downloaded ranges write at their absolute positions.
Out-of-order downloaded ranges write at their absolute positions · case 02
Out-of-order downloaded ranges write at their absolute positions.
Out-of-order downloaded ranges write at their absolute positions · case 03
Out-of-order downloaded ranges write at their absolute positions.
Out-of-order downloaded ranges write at their absolute positions · case 04
Out-of-order downloaded ranges write at their absolute positions.
Out-of-order downloaded ranges write at their absolute positions · case 05
Out-of-order downloaded ranges write at their absolute positions.
Download checkpoints advance only after durable writes · case 01
Download checkpoints advance only after durable writes.
Download checkpoints advance only after durable writes · case 02
Download checkpoints advance only after durable writes.
Download checkpoints advance only after durable writes · case 03
Download checkpoints advance only after durable writes.
Download checkpoints advance only after durable writes · case 04
Download checkpoints advance only after durable writes.
Download checkpoints advance only after durable writes · case 05
Download checkpoints advance only after durable writes.
A checkpoint beyond local file size must be discarded before a range request · case 01
A checkpoint beyond local file size must be discarded before a range request.
A checkpoint beyond local file size must be discarded before a range request · case 02
A checkpoint beyond local file size must be discarded before a range request.
A checkpoint beyond local file size must be discarded before a range request · case 03
A checkpoint beyond local file size must be discarded before a range request.
A checkpoint beyond local file size must be discarded before a range request · case 04
A checkpoint beyond local file size must be discarded before a range request.
A checkpoint beyond local file size must be discarded before a range request · case 05
A checkpoint beyond local file size must be discarded before a range request.
Saved byte positions cannot transfer across content encodings · case 01
Saved byte positions cannot transfer across content encodings.
Saved byte positions cannot transfer across content encodings · case 02
Saved byte positions cannot transfer across content encodings.
Saved byte positions cannot transfer across content encodings · case 03
Saved byte positions cannot transfer across content encodings.
Saved byte positions cannot transfer across content encodings · case 04
Saved byte positions cannot transfer across content encodings.
Saved byte positions cannot transfer across content encodings · case 05
Saved byte positions cannot transfer across content encodings.
Confirmed shorter complete representations truncate stale local suffix bytes · case 01
Confirmed shorter complete representations truncate stale local suffix bytes.
Confirmed shorter complete representations truncate stale local suffix bytes · case 02
Confirmed shorter complete representations truncate stale local suffix bytes.
Confirmed shorter complete representations truncate stale local suffix bytes · case 03
Confirmed shorter complete representations truncate stale local suffix bytes.
Confirmed shorter complete representations truncate stale local suffix bytes · case 04
Confirmed shorter complete representations truncate stale local suffix bytes.
Confirmed shorter complete representations truncate stale local suffix bytes · case 05
Confirmed shorter complete representations truncate stale local suffix bytes.
Completed byte positions count once across duplicate downloaded fragments · case 01
Completed byte positions count once across duplicate downloaded fragments.
Completed byte positions count once across duplicate downloaded fragments · case 02
Completed byte positions count once across duplicate downloaded fragments.
Completed byte positions count once across duplicate downloaded fragments · case 03
Completed byte positions count once across duplicate downloaded fragments.
Completed byte positions count once across duplicate downloaded fragments · case 04
Completed byte positions count once across duplicate downloaded fragments.
Completed byte positions count once across duplicate downloaded fragments · case 05
Completed byte positions count once across duplicate downloaded fragments.
Multipart boundary detection retains an incomplete delimiter suffix across reads · case 01
Multipart boundary detection retains an incomplete delimiter suffix across reads.
Multipart boundary detection retains an incomplete delimiter suffix across reads · case 02
Multipart boundary detection retains an incomplete delimiter suffix across reads.
Multipart boundary detection retains an incomplete delimiter suffix across reads · case 03
Multipart boundary detection retains an incomplete delimiter suffix across reads.
Multipart boundary detection retains an incomplete delimiter suffix across reads · case 04
Multipart boundary detection retains an incomplete delimiter suffix across reads.
Multipart boundary detection retains an incomplete delimiter suffix across reads · case 05
Multipart boundary detection retains an incomplete delimiter suffix across reads.
Boundary-like substrings inside part bodies remain payload data · case 01
Boundary-like substrings inside part bodies remain payload data.
Boundary-like substrings inside part bodies remain payload data · case 02
Boundary-like substrings inside part bodies remain payload data.
Boundary-like substrings inside part bodies remain payload data · case 03
Boundary-like substrings inside part bodies remain payload data.
Boundary-like substrings inside part bodies remain payload data · case 04
Boundary-like substrings inside part bodies remain payload data.
Boundary-like substrings inside part bodies remain payload data · case 05
Boundary-like substrings inside part bodies remain payload data.
INSPECTABLE BY DESIGN
Every result has a runnable source.
Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.
Read the methodology ↗