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
Concurrent download clients share bounded origin range reads: later ranges cannot displace an earlier request from the same consumer · case 01
Concurrent download clients share bounded origin range reads: later ranges cannot displace an earlier request from the same consumer.
Concurrent download clients share bounded origin range reads: later ranges cannot displace an earlier request from the same consumer · case 02
Concurrent download clients share bounded origin range reads: later ranges cannot displace an earlier request from the same consumer.
Concurrent download clients share bounded origin range reads: later ranges cannot displace an earlier request from the same consumer · case 03
Concurrent download clients share bounded origin range reads: later ranges cannot displace an earlier request from the same consumer.
Concurrent download clients share bounded origin range reads: later ranges cannot displace an earlier request from the same consumer · case 04
Concurrent download clients share bounded origin range reads: later ranges cannot displace an earlier request from the same consumer.
Concurrent download clients share bounded origin range reads: later ranges cannot displace an earlier request from the same consumer · case 05
Concurrent download clients share bounded origin range reads: later ranges cannot displace an earlier request from the same consumer.
Concurrent download clients share bounded origin range reads: a scheduling turn does not overrun its origin request slot allowance · case 01
Concurrent download clients share bounded origin range reads: a scheduling turn does not overrun its origin request slot allowance.
Concurrent download clients share bounded origin range reads: a scheduling turn does not overrun its origin request slot allowance · case 02
Concurrent download clients share bounded origin range reads: a scheduling turn does not overrun its origin request slot allowance.
Concurrent download clients share bounded origin range reads: a scheduling turn does not overrun its origin request slot allowance · case 03
Concurrent download clients share bounded origin range reads: a scheduling turn does not overrun its origin request slot allowance.
Concurrent download clients share bounded origin range reads: a scheduling turn does not overrun its origin request slot allowance · case 04
Concurrent download clients share bounded origin range reads: a scheduling turn does not overrun its origin request slot allowance.
Concurrent download clients share bounded origin range reads: a scheduling turn does not overrun its origin request slot allowance · case 05
Concurrent download clients share bounded origin range reads: a scheduling turn does not overrun its origin request slot allowance.
Concurrent download clients share bounded origin range reads: large byte requests are bounded by the origin chunk policy · case 01
Concurrent download clients share bounded origin range reads: large byte requests are bounded by the origin chunk policy.
Concurrent download clients share bounded origin range reads: large byte requests are bounded by the origin chunk policy · case 02
Concurrent download clients share bounded origin range reads: large byte requests are bounded by the origin chunk policy.
Concurrent download clients share bounded origin range reads: large byte requests are bounded by the origin chunk policy · case 03
Concurrent download clients share bounded origin range reads: large byte requests are bounded by the origin chunk policy.
Concurrent download clients share bounded origin range reads: large byte requests are bounded by the origin chunk policy · case 04
Concurrent download clients share bounded origin range reads: large byte requests are bounded by the origin chunk policy.
Concurrent download clients share bounded origin range reads: large byte requests are bounded by the origin chunk policy · case 05
Concurrent download clients share bounded origin range reads: large byte requests are bounded by the origin chunk policy.
Concurrent download clients share bounded origin range reads: only the completed front request is removed from a consumer queue · case 01
Concurrent download clients share bounded origin range reads: only the completed front request is removed from a consumer queue.
Concurrent download clients share bounded origin range reads: only the completed front request is removed from a consumer queue · case 02
Concurrent download clients share bounded origin range reads: only the completed front request is removed from a consumer queue.
Concurrent download clients share bounded origin range reads: only the completed front request is removed from a consumer queue · case 03
Concurrent download clients share bounded origin range reads: only the completed front request is removed from a consumer queue.
Concurrent download clients share bounded origin range reads: only the completed front request is removed from a consumer queue · case 04
Concurrent download clients share bounded origin range reads: only the completed front request is removed from a consumer queue.
Concurrent download clients share bounded origin range reads: only the completed front request is removed from a consumer queue · case 05
Concurrent download clients share bounded origin range reads: only the completed front request is removed from a consumer queue.
Concurrent download clients share bounded origin range reads: subsequent chunks advance their absolute origin byte start · case 01
Concurrent download clients share bounded origin range reads: subsequent chunks advance their absolute origin byte start.
Concurrent download clients share bounded origin range reads: subsequent chunks advance their absolute origin byte start · case 02
Concurrent download clients share bounded origin range reads: subsequent chunks advance their absolute origin byte start.
Concurrent download clients share bounded origin range reads: subsequent chunks advance their absolute origin byte start · case 03
Concurrent download clients share bounded origin range reads: subsequent chunks advance their absolute origin byte start.
Concurrent download clients share bounded origin range reads: subsequent chunks advance their absolute origin byte start · case 04
Concurrent download clients share bounded origin range reads: subsequent chunks advance their absolute origin byte start.
Concurrent download clients share bounded origin range reads: subsequent chunks advance their absolute origin byte start · case 05
Concurrent download clients share bounded origin range reads: subsequent chunks advance their absolute origin byte start.
Concurrent download clients share bounded origin range reads: scheduling consumes only the dispatched chunk from the request · case 01
Concurrent download clients share bounded origin range reads: scheduling consumes only the dispatched chunk from the request.
Concurrent download clients share bounded origin range reads: scheduling consumes only the dispatched chunk from the request · case 02
Concurrent download clients share bounded origin range reads: scheduling consumes only the dispatched chunk from the request.
Concurrent download clients share bounded origin range reads: scheduling consumes only the dispatched chunk from the request · case 03
Concurrent download clients share bounded origin range reads: scheduling consumes only the dispatched chunk from the request.
Concurrent download clients share bounded origin range reads: scheduling consumes only the dispatched chunk from the request · case 04
Concurrent download clients share bounded origin range reads: scheduling consumes only the dispatched chunk from the request.
Concurrent download clients share bounded origin range reads: scheduling consumes only the dispatched chunk from the request · case 05
Concurrent download clients share bounded origin range reads: scheduling consumes only the dispatched chunk from the request.
Concurrent download clients share bounded origin range reads: an unfinished large range yields the origin slot to other clients · case 01
Concurrent download clients share bounded origin range reads: an unfinished large range yields the origin slot to other clients.
Concurrent download clients share bounded origin range reads: an unfinished large range yields the origin slot to other clients · case 02
Concurrent download clients share bounded origin range reads: an unfinished large range yields the origin slot to other clients.
Concurrent download clients share bounded origin range reads: an unfinished large range yields the origin slot to other clients · case 03
Concurrent download clients share bounded origin range reads: an unfinished large range yields the origin slot to other clients.
Concurrent download clients share bounded origin range reads: an unfinished large range yields the origin slot to other clients · case 04
Concurrent download clients share bounded origin range reads: an unfinished large range yields the origin slot to other clients.
Concurrent download clients share bounded origin range reads: an unfinished large range yields the origin slot to other clients · case 05
Concurrent download clients share bounded origin range reads: an unfinished large range yields the origin slot to other clients.
Concurrent download clients share bounded origin range reads: undispatched requests from the same consumer survive the scheduling turn · case 01
Concurrent download clients share bounded origin range reads: undispatched requests from the same consumer survive the scheduling turn.
Concurrent download clients share bounded origin range reads: undispatched requests from the same consumer survive the scheduling turn · case 02
Concurrent download clients share bounded origin range reads: undispatched requests from the same consumer survive the scheduling turn.
Concurrent download clients share bounded origin range reads: undispatched requests from the same consumer survive the scheduling turn · case 03
Concurrent download clients share bounded origin range reads: undispatched requests from the same consumer survive the scheduling turn.
Concurrent download clients share bounded origin range reads: undispatched requests from the same consumer survive the scheduling turn · case 04
Concurrent download clients share bounded origin range reads: undispatched requests from the same consumer survive the scheduling turn.
Concurrent download clients share bounded origin range reads: undispatched requests from the same consumer survive the scheduling turn · case 05
Concurrent download clients share bounded origin range reads: undispatched requests from the same consumer survive the scheduling turn.
An origin adapter turns byte requests into bounded aligned storage reads: byte positions map by floor division into storage blocks · case 01
An origin adapter turns byte requests into bounded aligned storage reads: byte positions map by floor division into storage blocks.
An origin adapter turns byte requests into bounded aligned storage reads: byte positions map by floor division into storage blocks · case 02
An origin adapter turns byte requests into bounded aligned storage reads: byte positions map by floor division into storage blocks.
An origin adapter turns byte requests into bounded aligned storage reads: byte positions map by floor division into storage blocks · case 03
An origin adapter turns byte requests into bounded aligned storage reads: byte positions map by floor division into storage blocks.
An origin adapter turns byte requests into bounded aligned storage reads: byte positions map by floor division into storage blocks · case 04
An origin adapter turns byte requests into bounded aligned storage reads: byte positions map by floor division into storage blocks.
An origin adapter turns byte requests into bounded aligned storage reads: byte positions map by floor division into storage blocks · case 05
An origin adapter turns byte requests into bounded aligned storage reads: byte positions map by floor division into storage blocks.
An origin adapter turns byte requests into bounded aligned storage reads: slices retain their offset inside the first aligned block · case 01
An origin adapter turns byte requests into bounded aligned storage reads: slices retain their offset inside the first aligned block.
An origin adapter turns byte requests into bounded aligned storage reads: slices retain their offset inside the first aligned block · case 02
An origin adapter turns byte requests into bounded aligned storage reads: slices retain their offset inside the first aligned block.
An origin adapter turns byte requests into bounded aligned storage reads: slices retain their offset inside the first aligned block · case 03
An origin adapter turns byte requests into bounded aligned storage reads: slices retain their offset inside the first aligned block.
An origin adapter turns byte requests into bounded aligned storage reads: slices retain their offset inside the first aligned block · case 04
An origin adapter turns byte requests into bounded aligned storage reads: slices retain their offset inside the first aligned block.
An origin adapter turns byte requests into bounded aligned storage reads: slices retain their offset inside the first aligned block · case 05
An origin adapter turns byte requests into bounded aligned storage reads: slices retain their offset inside the first aligned block.
An origin adapter turns byte requests into bounded aligned storage reads: each slice stops at the current storage block boundary · case 01
An origin adapter turns byte requests into bounded aligned storage reads: each slice stops at the current storage block boundary.
An origin adapter turns byte requests into bounded aligned storage reads: each slice stops at the current storage block boundary · case 02
An origin adapter turns byte requests into bounded aligned storage reads: each slice stops at the current storage block boundary.
An origin adapter turns byte requests into bounded aligned storage reads: each slice stops at the current storage block boundary · case 03
An origin adapter turns byte requests into bounded aligned storage reads: each slice stops at the current storage block boundary.
An origin adapter turns byte requests into bounded aligned storage reads: each slice stops at the current storage block boundary · case 04
An origin adapter turns byte requests into bounded aligned storage reads: each slice stops at the current storage block boundary.
An origin adapter turns byte requests into bounded aligned storage reads: each slice stops at the current storage block boundary · case 05
An origin adapter turns byte requests into bounded aligned storage reads: each slice stops at the current storage block boundary.
An origin adapter turns byte requests into bounded aligned storage reads: one request keeps all of its crossed block slices · case 01
An origin adapter turns byte requests into bounded aligned storage reads: one request keeps all of its crossed block slices.
An origin adapter turns byte requests into bounded aligned storage reads: one request keeps all of its crossed block slices · case 02
An origin adapter turns byte requests into bounded aligned storage reads: one request keeps all of its crossed block slices.
An origin adapter turns byte requests into bounded aligned storage reads: one request keeps all of its crossed block slices · case 03
An origin adapter turns byte requests into bounded aligned storage reads: one request keeps all of its crossed block slices.
An origin adapter turns byte requests into bounded aligned storage reads: one request keeps all of its crossed block slices · case 04
An origin adapter turns byte requests into bounded aligned storage reads: one request keeps all of its crossed block slices.
An origin adapter turns byte requests into bounded aligned storage reads: one request keeps all of its crossed block slices · case 05
An origin adapter turns byte requests into bounded aligned storage reads: one request keeps all of its crossed block slices.
An origin adapter turns byte requests into bounded aligned storage reads: every crossed block contributes to the origin fetch set · case 01
An origin adapter turns byte requests into bounded aligned storage reads: every crossed block contributes to the origin fetch set.
An origin adapter turns byte requests into bounded aligned storage reads: every crossed block contributes to the origin fetch set · case 02
An origin adapter turns byte requests into bounded aligned storage reads: every crossed block contributes to the origin fetch set.
An origin adapter turns byte requests into bounded aligned storage reads: every crossed block contributes to the origin fetch set · case 03
An origin adapter turns byte requests into bounded aligned storage reads: every crossed block contributes to the origin fetch set.
An origin adapter turns byte requests into bounded aligned storage reads: every crossed block contributes to the origin fetch set · case 04
An origin adapter turns byte requests into bounded aligned storage reads: every crossed block contributes to the origin fetch set.
An origin adapter turns byte requests into bounded aligned storage reads: every crossed block contributes to the origin fetch set · case 05
An origin adapter turns byte requests into bounded aligned storage reads: every crossed block contributes to the origin fetch set.
An origin adapter turns byte requests into bounded aligned storage reads: the next block slice begins after bytes actually mapped · case 01
An origin adapter turns byte requests into bounded aligned storage reads: the next block slice begins after bytes actually mapped.
An origin adapter turns byte requests into bounded aligned storage reads: the next block slice begins after bytes actually mapped · case 02
An origin adapter turns byte requests into bounded aligned storage reads: the next block slice begins after bytes actually mapped.
An origin adapter turns byte requests into bounded aligned storage reads: the next block slice begins after bytes actually mapped · case 03
An origin adapter turns byte requests into bounded aligned storage reads: the next block slice begins after bytes actually mapped.
An origin adapter turns byte requests into bounded aligned storage reads: the next block slice begins after bytes actually mapped · case 04
An origin adapter turns byte requests into bounded aligned storage reads: the next block slice begins after bytes actually mapped.
An origin adapter turns byte requests into bounded aligned storage reads: the next block slice begins after bytes actually mapped · case 05
An origin adapter turns byte requests into bounded aligned storage reads: the next block slice begins after bytes actually mapped.
An origin adapter turns byte requests into bounded aligned storage reads: empty byte requests retain their location in the response plan · case 01
An origin adapter turns byte requests into bounded aligned storage reads: empty byte requests retain their location in the response plan.
An origin adapter turns byte requests into bounded aligned storage reads: empty byte requests retain their location in the response plan · case 02
An origin adapter turns byte requests into bounded aligned storage reads: empty byte requests retain their location in the response plan.
An origin adapter turns byte requests into bounded aligned storage reads: empty byte requests retain their location in the response plan · case 03
An origin adapter turns byte requests into bounded aligned storage reads: empty byte requests retain their location in the response plan.
An origin adapter turns byte requests into bounded aligned storage reads: empty byte requests retain their location in the response plan · case 04
An origin adapter turns byte requests into bounded aligned storage reads: empty byte requests retain their location in the response plan.
An origin adapter turns byte requests into bounded aligned storage reads: empty byte requests retain their location in the response plan · case 05
An origin adapter turns byte requests into bounded aligned storage reads: empty byte requests retain their location in the response plan.
An origin adapter turns byte requests into bounded aligned storage reads: cached blocks retain slice mappings while skipping origin reads · case 01
An origin adapter turns byte requests into bounded aligned storage reads: cached blocks retain slice mappings while skipping origin reads.
An origin adapter turns byte requests into bounded aligned storage reads: cached blocks retain slice mappings while skipping origin reads · case 02
An origin adapter turns byte requests into bounded aligned storage reads: cached blocks retain slice mappings while skipping origin reads.
An origin adapter turns byte requests into bounded aligned storage reads: cached blocks retain slice mappings while skipping origin reads · case 03
An origin adapter turns byte requests into bounded aligned storage reads: cached blocks retain slice mappings while skipping origin reads.
An origin adapter turns byte requests into bounded aligned storage reads: cached blocks retain slice mappings while skipping origin reads · case 04
An origin adapter turns byte requests into bounded aligned storage reads: cached blocks retain slice mappings while skipping origin reads.
An origin adapter turns byte requests into bounded aligned storage reads: cached blocks retain slice mappings while skipping origin reads · case 05
An origin adapter turns byte requests into bounded aligned storage reads: cached blocks retain slice mappings while skipping origin reads.
An origin adapter turns byte requests into bounded aligned storage reads: physical reads begin at the block base in the object · case 01
An origin adapter turns byte requests into bounded aligned storage reads: physical reads begin at the block base in the object.
An origin adapter turns byte requests into bounded aligned storage reads: physical reads begin at the block base in the object · case 02
An origin adapter turns byte requests into bounded aligned storage reads: physical reads begin at the block base in the object.
An origin adapter turns byte requests into bounded aligned storage reads: physical reads begin at the block base in the object · case 03
An origin adapter turns byte requests into bounded aligned storage reads: physical reads begin at the block base in the object.
An origin adapter turns byte requests into bounded aligned storage reads: physical reads begin at the block base in the object · case 04
An origin adapter turns byte requests into bounded aligned storage reads: physical reads begin at the block base in the object.
An origin adapter turns byte requests into bounded aligned storage reads: physical reads begin at the block base in the object · case 05
An origin adapter turns byte requests into bounded aligned storage reads: physical reads begin at the block base in the object.
An origin adapter turns byte requests into bounded aligned storage reads: the final storage block does not read beyond representation EOF · case 01
An origin adapter turns byte requests into bounded aligned storage reads: the final storage block does not read beyond representation EOF.
An origin adapter turns byte requests into bounded aligned storage reads: the final storage block does not read beyond representation EOF · case 02
An origin adapter turns byte requests into bounded aligned storage reads: the final storage block does not read beyond representation EOF.
An origin adapter turns byte requests into bounded aligned storage reads: the final storage block does not read beyond representation EOF · case 03
An origin adapter turns byte requests into bounded aligned storage reads: the final storage block does not read beyond representation EOF.
An origin adapter turns byte requests into bounded aligned storage reads: the final storage block does not read beyond representation EOF · case 04
An origin adapter turns byte requests into bounded aligned storage reads: the final storage block does not read beyond representation EOF.
An origin adapter turns byte requests into bounded aligned storage reads: the final storage block does not read beyond representation EOF · case 05
An origin adapter turns byte requests into bounded aligned storage reads: the final storage block does not read beyond representation EOF.
A range client removes transfer framing before applying representation offsets: chunk lengths use hexadecimal representation · case 01
A range client removes transfer framing before applying representation offsets: chunk lengths use hexadecimal representation.
A range client removes transfer framing before applying representation offsets: chunk lengths use hexadecimal representation · case 02
A range client removes transfer framing before applying representation offsets: chunk lengths use hexadecimal representation.
A range client removes transfer framing before applying representation offsets: chunk lengths use hexadecimal representation · case 03
A range client removes transfer framing before applying representation offsets: chunk lengths use hexadecimal representation.
A range client removes transfer framing before applying representation offsets: chunk lengths use hexadecimal representation · case 04
A range client removes transfer framing before applying representation offsets: chunk lengths use hexadecimal representation.
A range client removes transfer framing before applying representation offsets: chunk lengths use hexadecimal representation · case 05
A range client removes transfer framing before applying representation offsets: chunk lengths use hexadecimal representation.
A range client removes transfer framing before applying representation offsets: chunk extensions do not become part of the size token · case 01
A range client removes transfer framing before applying representation offsets: chunk extensions do not become part of the size token.
A range client removes transfer framing before applying representation offsets: chunk extensions do not become part of the size token · case 02
A range client removes transfer framing before applying representation offsets: chunk extensions do not become part of the size token.
A range client removes transfer framing before applying representation offsets: chunk extensions do not become part of the size token · case 03
A range client removes transfer framing before applying representation offsets: chunk extensions do not become part of the size token.
A range client removes transfer framing before applying representation offsets: chunk extensions do not become part of the size token · case 04
A range client removes transfer framing before applying representation offsets: chunk extensions do not become part of the size token.
A range client removes transfer framing before applying representation offsets: chunk extensions do not become part of the size token · case 05
A range client removes transfer framing before applying representation offsets: chunk extensions do not become part of the size token.
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 ↗