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
Missing cached bytes remain unavailable instead of becoming zero bytes · case 01
Missing cached bytes remain unavailable instead of becoming zero bytes.
Missing cached bytes remain unavailable instead of becoming zero bytes · case 02
Missing cached bytes remain unavailable instead of becoming zero bytes.
Missing cached bytes remain unavailable instead of becoming zero bytes · case 03
Missing cached bytes remain unavailable instead of becoming zero bytes.
Missing cached bytes remain unavailable instead of becoming zero bytes · case 04
Missing cached bytes remain unavailable instead of becoming zero bytes.
Missing cached bytes remain unavailable instead of becoming zero bytes · case 05
Missing cached bytes remain unavailable instead of becoming zero bytes.
Fragment admission rejects a conflicting complete length · case 01
Fragment admission rejects a conflicting complete length.
Fragment admission rejects a conflicting complete length · case 02
Fragment admission rejects a conflicting complete length.
Fragment admission rejects a conflicting complete length · case 03
Fragment admission rejects a conflicting complete length.
Fragment admission rejects a conflicting complete length · case 04
Fragment admission rejects a conflicting complete length.
Fragment admission rejects a conflicting complete length · case 05
Fragment admission rejects a conflicting complete length.
A stitched response exposes the oldest contributing fragment age · case 01
A stitched response exposes the oldest contributing fragment age.
A stitched response exposes the oldest contributing fragment age · case 02
A stitched response exposes the oldest contributing fragment age.
A stitched response exposes the oldest contributing fragment age · case 03
A stitched response exposes the oldest contributing fragment age.
A stitched response exposes the oldest contributing fragment age · case 04
A stitched response exposes the oldest contributing fragment age.
A stitched response exposes the oldest contributing fragment age · case 05
A stitched response exposes the oldest contributing fragment age.
Assembly expires with its earliest expiring fragment · case 01
Assembly expires with its earliest expiring fragment.
Assembly expires with its earliest expiring fragment · case 02
Assembly expires with its earliest expiring fragment.
Assembly expires with its earliest expiring fragment · case 03
Assembly expires with its earliest expiring fragment.
Assembly expires with its earliest expiring fragment · case 04
Assembly expires with its earliest expiring fragment.
Assembly expires with its earliest expiring fragment · case 05
Assembly expires with its earliest expiring fragment.
User-specific partial objects remain partitioned by principal · case 01
User-specific partial objects remain partitioned by principal.
User-specific partial objects remain partitioned by principal · case 02
User-specific partial objects remain partitioned by principal.
User-specific partial objects remain partitioned by principal · case 03
User-specific partial objects remain partitioned by principal.
User-specific partial objects remain partitioned by principal · case 04
User-specific partial objects remain partitioned by principal.
User-specific partial objects remain partitioned by principal · case 05
User-specific partial objects remain partitioned by principal.
A wildcard Vary response is not stored as a reusable partial object · case 01
A wildcard Vary response is not stored as a reusable partial object.
A wildcard Vary response is not stored as a reusable partial object · case 02
A wildcard Vary response is not stored as a reusable partial object.
A wildcard Vary response is not stored as a reusable partial object · case 03
A wildcard Vary response is not stored as a reusable partial object.
A wildcard Vary response is not stored as a reusable partial object · case 04
A wildcard Vary response is not stored as a reusable partial object.
A wildcard Vary response is not stored as a reusable partial object · case 05
A wildcard Vary response is not stored as a reusable partial object.
A fresh full response replaces all stale sparse fragments · case 01
A fresh full response replaces all stale sparse fragments.
A fresh full response replaces all stale sparse fragments · case 02
A fresh full response replaces all stale sparse fragments.
A fresh full response replaces all stale sparse fragments · case 03
A fresh full response replaces all stale sparse fragments.
A fresh full response replaces all stale sparse fragments · case 04
A fresh full response replaces all stale sparse fragments.
A fresh full response replaces all stale sparse fragments · case 05
A fresh full response replaces all stale sparse fragments.
No-store metadata prevents partial staging from surviving admission · case 01
No-store metadata prevents partial staging from surviving admission.
No-store metadata prevents partial staging from surviving admission · case 02
No-store metadata prevents partial staging from surviving admission.
No-store metadata prevents partial staging from surviving admission · case 03
No-store metadata prevents partial staging from surviving admission.
No-store metadata prevents partial staging from surviving admission · case 04
No-store metadata prevents partial staging from surviving admission.
No-store metadata prevents partial staging from surviving admission · case 05
No-store metadata prevents partial staging from surviving admission.
A short socket write preserves the unsent byte suffix · case 01
A short socket write preserves the unsent byte suffix.
A short socket write preserves the unsent byte suffix · case 02
A short socket write preserves the unsent byte suffix.
A short socket write preserves the unsent byte suffix · case 03
A short socket write preserves the unsent byte suffix.
A short socket write preserves the unsent byte suffix · case 04
A short socket write preserves the unsent byte suffix.
A short socket write preserves the unsent byte suffix · case 05
A short socket write preserves the unsent byte suffix.
Read-ahead respects both stream credit and remaining range bytes · case 01
Read-ahead respects both stream credit and remaining range bytes.
Read-ahead respects both stream credit and remaining range bytes · case 02
Read-ahead respects both stream credit and remaining range bytes.
Read-ahead respects both stream credit and remaining range bytes · case 03
Read-ahead respects both stream credit and remaining range bytes.
Read-ahead respects both stream credit and remaining range bytes · case 04
Read-ahead respects both stream credit and remaining range bytes.
Read-ahead respects both stream credit and remaining range bytes · case 05
Read-ahead respects both stream credit and remaining range bytes.
Partial-read progress advances from the selected absolute start · case 01
Partial-read progress advances from the selected absolute start.
Partial-read progress advances from the selected absolute start · case 02
Partial-read progress advances from the selected absolute start.
Partial-read progress advances from the selected absolute start · case 03
Partial-read progress advances from the selected absolute start.
Partial-read progress advances from the selected absolute start · case 04
Partial-read progress advances from the selected absolute start.
Partial-read progress advances from the selected absolute start · case 05
Partial-read progress advances from the selected absolute start.
Multipart framing bytes do not advance the representation cursor · case 01
Multipart framing bytes do not advance the representation cursor.
Multipart framing bytes do not advance the representation cursor · case 02
Multipart framing bytes do not advance the representation cursor.
Multipart framing bytes do not advance the representation cursor · case 03
Multipart framing bytes do not advance the representation cursor.
Multipart framing bytes do not advance the representation cursor · case 04
Multipart framing bytes do not advance the representation cursor.
Multipart framing bytes do not advance the representation cursor · case 05
Multipart framing bytes do not advance the representation cursor.
EOF before the promised range length marks the stream truncated · case 01
EOF before the promised range length marks the stream truncated.
EOF before the promised range length marks the stream truncated · case 02
EOF before the promised range length marks the stream truncated.
EOF before the promised range length marks the stream truncated · case 03
EOF before the promised range length marks the stream truncated.
EOF before the promised range length marks the stream truncated · case 04
EOF before the promised range length marks the stream truncated.
EOF before the promised range length marks the stream truncated · case 05
EOF before the promised range length marks the stream truncated.
A would-block read does not mean representation EOF · case 01
A would-block read does not mean representation EOF.
A would-block read does not mean representation EOF · case 02
A would-block read does not mean representation EOF.
A would-block read does not mean representation EOF · case 03
A would-block read does not mean representation EOF.
A would-block read does not mean representation EOF · case 04
A would-block read does not mean representation EOF.
A would-block read does not mean representation EOF · case 05
A would-block read does not mean representation EOF.
Canceled range streams release snapshot pins and pending data · case 01
Canceled range streams release snapshot pins and pending data.
Canceled range streams release snapshot pins and pending data · case 02
Canceled range streams release snapshot pins and pending data.
Canceled range streams release snapshot pins and pending data · case 03
Canceled range streams release snapshot pins and pending data.
Canceled range streams release snapshot pins and pending data · case 04
Canceled range streams release snapshot pins and pending data.
Canceled range streams release snapshot pins and pending data · case 05
Canceled range streams release snapshot pins and pending data.
Repeated close events release a range handle only once · case 01
Repeated close events release a range handle only once.
Repeated close events release a range handle only once · case 02
Repeated close events release a range handle only once.
Repeated close events release a range handle only once · case 03
Repeated close events release a range handle only once.
Repeated close events release a range handle only once · case 04
Repeated close events release a range handle only once.
Repeated close events release a range handle only once · case 05
Repeated close events release a range handle only once.
Representation checksum excludes multipart envelope bytes · case 01
Representation checksum excludes multipart envelope bytes.
Representation checksum excludes multipart envelope bytes · case 02
Representation checksum excludes multipart envelope bytes.
Representation checksum excludes multipart envelope bytes · case 03
Representation checksum excludes multipart envelope bytes.
Representation checksum excludes multipart envelope bytes · case 04
Representation checksum excludes multipart envelope bytes.
Representation checksum excludes multipart envelope bytes · case 05
Representation checksum excludes multipart envelope bytes.
Errors after partial headers abort instead of injecting a second response · case 01
Errors after partial headers abort instead of injecting a second response.
Errors after partial headers abort instead of injecting a second response · case 02
Errors after partial headers abort instead of injecting a second response.
Errors after partial headers abort instead of injecting a second response · case 03
Errors after partial headers abort instead of injecting a second response.
Errors after partial headers abort instead of injecting a second response · case 04
Errors after partial headers abort instead of injecting a second response.
Errors after partial headers abort instead of injecting a second response · case 05
Errors after partial headers abort instead of injecting a second response.
Integrity trailers are emitted only after all promised bytes arrive · case 01
Integrity trailers are emitted only after all promised bytes arrive.
Integrity trailers are emitted only after all promised bytes arrive · case 02
Integrity trailers are emitted only after all promised bytes arrive.
Integrity trailers are emitted only after all promised bytes arrive · case 03
Integrity trailers are emitted only after all promised bytes arrive.
Integrity trailers are emitted only after all promised bytes arrive · case 04
Integrity trailers are emitted only after all promised bytes arrive.
Integrity trailers are emitted only after all promised bytes arrive · case 05
Integrity trailers are emitted only after all promised bytes arrive.
Oversized backend reads do not leak bytes outside the response budget · case 01
Oversized backend reads do not leak bytes outside the response budget.
Oversized backend reads do not leak bytes outside the response budget · case 02
Oversized backend reads do not leak bytes outside the response budget.
Oversized backend reads do not leak bytes outside the response budget · case 03
Oversized backend reads do not leak bytes outside the response budget.
Oversized backend reads do not leak bytes outside the response budget · case 04
Oversized backend reads do not leak bytes outside the response budget.
Oversized backend reads do not leak bytes outside the response budget · case 05
Oversized backend reads do not leak bytes outside the response budget.
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 ↗