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
A client serializes a typed range request plan: suffix counts are introduced by a leading dash · case 01
A client serializes a typed range request plan: suffix counts are introduced by a leading dash.
A client serializes a typed range request plan: suffix counts are introduced by a leading dash · case 02
A client serializes a typed range request plan: suffix counts are introduced by a leading dash.
A client serializes a typed range request plan: suffix counts are introduced by a leading dash · case 03
A client serializes a typed range request plan: suffix counts are introduced by a leading dash.
A client serializes a typed range request plan: suffix counts are introduced by a leading dash · case 04
A client serializes a typed range request plan: suffix counts are introduced by a leading dash.
A client serializes a typed range request plan: suffix counts are introduced by a leading dash · case 05
A client serializes a typed range request plan: suffix counts are introduced by a leading dash.
A client serializes a typed range request plan: outbound members preserve caller priority order · case 01
A client serializes a typed range request plan: outbound members preserve caller priority order.
A client serializes a typed range request plan: outbound members preserve caller priority order · case 02
A client serializes a typed range request plan: outbound members preserve caller priority order.
A client serializes a typed range request plan: outbound members preserve caller priority order · case 03
A client serializes a typed range request plan: outbound members preserve caller priority order.
A client serializes a typed range request plan: outbound members preserve caller priority order · case 04
A client serializes a typed range request plan: outbound members preserve caller priority order.
A client serializes a typed range request plan: outbound members preserve caller priority order · case 05
A client serializes a typed range request plan: outbound members preserve caller priority order.
A client serializes a typed range request plan: multiple members share a single comma-separated field · case 01
A client serializes a typed range request plan: multiple members share a single comma-separated field.
A client serializes a typed range request plan: multiple members share a single comma-separated field · case 02
A client serializes a typed range request plan: multiple members share a single comma-separated field.
A client serializes a typed range request plan: multiple members share a single comma-separated field · case 03
A client serializes a typed range request plan: multiple members share a single comma-separated field.
A client serializes a typed range request plan: multiple members share a single comma-separated field · case 04
A client serializes a typed range request plan: multiple members share a single comma-separated field.
A client serializes a typed range request plan: multiple members share a single comma-separated field · case 05
A client serializes a typed range request plan: multiple members share a single comma-separated field.
A client serializes a typed range request plan: Range requests do not send response-only Content-Range fields · case 01
A client serializes a typed range request plan: Range requests do not send response-only Content-Range fields.
A client serializes a typed range request plan: Range requests do not send response-only Content-Range fields · case 02
A client serializes a typed range request plan: Range requests do not send response-only Content-Range fields.
A client serializes a typed range request plan: Range requests do not send response-only Content-Range fields · case 03
A client serializes a typed range request plan: Range requests do not send response-only Content-Range fields.
A client serializes a typed range request plan: Range requests do not send response-only Content-Range fields · case 04
A client serializes a typed range request plan: Range requests do not send response-only Content-Range fields.
A client serializes a typed range request plan: Range requests do not send response-only Content-Range fields · case 05
A client serializes a typed range request plan: Range requests do not send response-only Content-Range fields.
A client serializes a typed range request plan: an empty selector plan emits no conditional range field · case 01
A client serializes a typed range request plan: an empty selector plan emits no conditional range field.
A client serializes a typed range request plan: an empty selector plan emits no conditional range field · case 02
A client serializes a typed range request plan: an empty selector plan emits no conditional range field.
A client serializes a typed range request plan: an empty selector plan emits no conditional range field · case 03
A client serializes a typed range request plan: an empty selector plan emits no conditional range field.
A client serializes a typed range request plan: an empty selector plan emits no conditional range field · case 04
A client serializes a typed range request plan: an empty selector plan emits no conditional range field.
A client serializes a typed range request plan: an empty selector plan emits no conditional range field · case 05
A client serializes a typed range request plan: an empty selector plan emits no conditional range field.
A client serializes a typed range request plan: entity validators retain their quoted wire form · case 01
A client serializes a typed range request plan: entity validators retain their quoted wire form.
A client serializes a typed range request plan: entity validators retain their quoted wire form · case 02
A client serializes a typed range request plan: entity validators retain their quoted wire form.
A client serializes a typed range request plan: entity validators retain their quoted wire form · case 03
A client serializes a typed range request plan: entity validators retain their quoted wire form.
A client serializes a typed range request plan: entity validators retain their quoted wire form · case 04
A client serializes a typed range request plan: entity validators retain their quoted wire form.
A client serializes a typed range request plan: entity validators retain their quoted wire form · case 05
A client serializes a typed range request plan: entity validators retain their quoted wire form.
A client serializes a typed range request plan: date validators are not serialized as opaque entity tags · case 01
A client serializes a typed range request plan: date validators are not serialized as opaque entity tags.
A client serializes a typed range request plan: date validators are not serialized as opaque entity tags · case 02
A client serializes a typed range request plan: date validators are not serialized as opaque entity tags.
A client serializes a typed range request plan: date validators are not serialized as opaque entity tags · case 03
A client serializes a typed range request plan: date validators are not serialized as opaque entity tags.
A client serializes a typed range request plan: date validators are not serialized as opaque entity tags · case 04
A client serializes a typed range request plan: date validators are not serialized as opaque entity tags.
A client serializes a typed range request plan: date validators are not serialized as opaque entity tags · case 05
A client serializes a typed range request plan: date validators are not serialized as opaque entity tags.
A client serializes a typed range request plan: byte-stable downloads request identity when configured · case 01
A client serializes a typed range request plan: byte-stable downloads request identity when configured.
A client serializes a typed range request plan: byte-stable downloads request identity when configured · case 02
A client serializes a typed range request plan: byte-stable downloads request identity when configured.
A client serializes a typed range request plan: byte-stable downloads request identity when configured · case 03
A client serializes a typed range request plan: byte-stable downloads request identity when configured.
A client serializes a typed range request plan: byte-stable downloads request identity when configured · case 04
A client serializes a typed range request plan: byte-stable downloads request identity when configured.
A client serializes a typed range request plan: byte-stable downloads request identity when configured · case 05
A client serializes a typed range request plan: byte-stable downloads request identity when configured.
A proxy coalesces nearby requested spans into economical origin reads: unsorted wire order must not drive origin coalescing · case 01
A proxy coalesces nearby requested spans into economical origin reads: unsorted wire order must not drive origin coalescing.
A proxy coalesces nearby requested spans into economical origin reads: unsorted wire order must not drive origin coalescing · case 02
A proxy coalesces nearby requested spans into economical origin reads: unsorted wire order must not drive origin coalescing.
A proxy coalesces nearby requested spans into economical origin reads: unsorted wire order must not drive origin coalescing · case 03
A proxy coalesces nearby requested spans into economical origin reads: unsorted wire order must not drive origin coalescing.
A proxy coalesces nearby requested spans into economical origin reads: unsorted wire order must not drive origin coalescing · case 04
A proxy coalesces nearby requested spans into economical origin reads: unsorted wire order must not drive origin coalescing.
A proxy coalesces nearby requested spans into economical origin reads: unsorted wire order must not drive origin coalescing · case 05
A proxy coalesces nearby requested spans into economical origin reads: unsorted wire order must not drive origin coalescing.
A proxy coalesces nearby requested spans into economical origin reads: empty logical selectors must not allocate backend fetches · case 01
A proxy coalesces nearby requested spans into economical origin reads: empty logical selectors must not allocate backend fetches.
A proxy coalesces nearby requested spans into economical origin reads: empty logical selectors must not allocate backend fetches · case 02
A proxy coalesces nearby requested spans into economical origin reads: empty logical selectors must not allocate backend fetches.
A proxy coalesces nearby requested spans into economical origin reads: empty logical selectors must not allocate backend fetches · case 03
A proxy coalesces nearby requested spans into economical origin reads: empty logical selectors must not allocate backend fetches.
A proxy coalesces nearby requested spans into economical origin reads: empty logical selectors must not allocate backend fetches · case 04
A proxy coalesces nearby requested spans into economical origin reads: empty logical selectors must not allocate backend fetches.
A proxy coalesces nearby requested spans into economical origin reads: empty logical selectors must not allocate backend fetches · case 05
A proxy coalesces nearby requested spans into economical origin reads: empty logical selectors must not allocate backend fetches.
A proxy coalesces nearby requested spans into economical origin reads: reads at the configured merge gap remain eligible · case 01
A proxy coalesces nearby requested spans into economical origin reads: reads at the configured merge gap remain eligible.
A proxy coalesces nearby requested spans into economical origin reads: reads at the configured merge gap remain eligible · case 02
A proxy coalesces nearby requested spans into economical origin reads: reads at the configured merge gap remain eligible.
A proxy coalesces nearby requested spans into economical origin reads: reads at the configured merge gap remain eligible · case 03
A proxy coalesces nearby requested spans into economical origin reads: reads at the configured merge gap remain eligible.
A proxy coalesces nearby requested spans into economical origin reads: reads at the configured merge gap remain eligible · case 04
A proxy coalesces nearby requested spans into economical origin reads: reads at the configured merge gap remain eligible.
A proxy coalesces nearby requested spans into economical origin reads: reads at the configured merge gap remain eligible · case 05
A proxy coalesces nearby requested spans into economical origin reads: reads at the configured merge gap remain eligible.
A proxy coalesces nearby requested spans into economical origin reads: coalescing cannot fetch forbidden bytes absent from requested payloads · case 01
A proxy coalesces nearby requested spans into economical origin reads: coalescing cannot fetch forbidden bytes absent from requested payloads.
A proxy coalesces nearby requested spans into economical origin reads: coalescing cannot fetch forbidden bytes absent from requested payloads · case 02
A proxy coalesces nearby requested spans into economical origin reads: coalescing cannot fetch forbidden bytes absent from requested payloads.
A proxy coalesces nearby requested spans into economical origin reads: coalescing cannot fetch forbidden bytes absent from requested payloads · case 03
A proxy coalesces nearby requested spans into economical origin reads: coalescing cannot fetch forbidden bytes absent from requested payloads.
A proxy coalesces nearby requested spans into economical origin reads: coalescing cannot fetch forbidden bytes absent from requested payloads · case 04
A proxy coalesces nearby requested spans into economical origin reads: coalescing cannot fetch forbidden bytes absent from requested payloads.
A proxy coalesces nearby requested spans into economical origin reads: coalescing cannot fetch forbidden bytes absent from requested payloads · case 05
A proxy coalesces nearby requested spans into economical origin reads: coalescing cannot fetch forbidden bytes absent from requested payloads.
A proxy coalesces nearby requested spans into economical origin reads: contained requests must not shrink a larger origin read · case 01
A proxy coalesces nearby requested spans into economical origin reads: contained requests must not shrink a larger origin read.
A proxy coalesces nearby requested spans into economical origin reads: contained requests must not shrink a larger origin read · case 02
A proxy coalesces nearby requested spans into economical origin reads: contained requests must not shrink a larger origin read.
A proxy coalesces nearby requested spans into economical origin reads: contained requests must not shrink a larger origin read · case 03
A proxy coalesces nearby requested spans into economical origin reads: contained requests must not shrink a larger origin read.
A proxy coalesces nearby requested spans into economical origin reads: contained requests must not shrink a larger origin read · case 04
A proxy coalesces nearby requested spans into economical origin reads: contained requests must not shrink a larger origin read.
A proxy coalesces nearby requested spans into economical origin reads: contained requests must not shrink a larger origin read · case 05
A proxy coalesces nearby requested spans into economical origin reads: contained requests must not shrink a larger origin read.
A proxy coalesces nearby requested spans into economical origin reads: new fetches map to their newly allocated index · case 01
A proxy coalesces nearby requested spans into economical origin reads: new fetches map to their newly allocated index.
A proxy coalesces nearby requested spans into economical origin reads: new fetches map to their newly allocated index · case 02
A proxy coalesces nearby requested spans into economical origin reads: new fetches map to their newly allocated index.
A proxy coalesces nearby requested spans into economical origin reads: new fetches map to their newly allocated index · case 03
A proxy coalesces nearby requested spans into economical origin reads: new fetches map to their newly allocated index.
A proxy coalesces nearby requested spans into economical origin reads: new fetches map to their newly allocated index · case 04
A proxy coalesces nearby requested spans into economical origin reads: new fetches map to their newly allocated index.
A proxy coalesces nearby requested spans into economical origin reads: new fetches map to their newly allocated index · case 05
A proxy coalesces nearby requested spans into economical origin reads: new fetches map to their newly allocated index.
A proxy coalesces nearby requested spans into economical origin reads: fetch mappings are returned in caller order after read sorting · case 01
A proxy coalesces nearby requested spans into economical origin reads: fetch mappings are returned in caller order after read sorting.
A proxy coalesces nearby requested spans into economical origin reads: fetch mappings are returned in caller order after read sorting · case 02
A proxy coalesces nearby requested spans into economical origin reads: fetch mappings are returned in caller order after read sorting.
A proxy coalesces nearby requested spans into economical origin reads: fetch mappings are returned in caller order after read sorting · case 03
A proxy coalesces nearby requested spans into economical origin reads: fetch mappings are returned in caller order after read sorting.
A proxy coalesces nearby requested spans into economical origin reads: fetch mappings are returned in caller order after read sorting · case 04
A proxy coalesces nearby requested spans into economical origin reads: fetch mappings are returned in caller order after read sorting.
A proxy coalesces nearby requested spans into economical origin reads: fetch mappings are returned in caller order after read sorting · case 05
A proxy coalesces nearby requested spans into economical origin reads: fetch mappings are returned in caller order after read sorting.
A proxy coalesces nearby requested spans into economical origin reads: caller slices use offsets relative to the containing fetch · case 01
A proxy coalesces nearby requested spans into economical origin reads: caller slices use offsets relative to the containing fetch.
A proxy coalesces nearby requested spans into economical origin reads: caller slices use offsets relative to the containing fetch · case 02
A proxy coalesces nearby requested spans into economical origin reads: caller slices use offsets relative to the containing fetch.
A proxy coalesces nearby requested spans into economical origin reads: caller slices use offsets relative to the containing fetch · case 03
A proxy coalesces nearby requested spans into economical origin reads: caller slices use offsets relative to the containing fetch.
A proxy coalesces nearby requested spans into economical origin reads: caller slices use offsets relative to the containing fetch · case 04
A proxy coalesces nearby requested spans into economical origin reads: caller slices use offsets relative to the containing fetch.
A proxy coalesces nearby requested spans into economical origin reads: caller slices use offsets relative to the containing fetch · case 05
A proxy coalesces nearby requested spans into economical origin reads: caller slices use offsets relative to the containing fetch.
A proxy coalesces nearby requested spans into economical origin reads: caller slice length excludes coalesced unrequested gap bytes · case 01
A proxy coalesces nearby requested spans into economical origin reads: caller slice length excludes coalesced unrequested gap bytes.
A proxy coalesces nearby requested spans into economical origin reads: caller slice length excludes coalesced unrequested gap bytes · case 02
A proxy coalesces nearby requested spans into economical origin reads: caller slice length excludes coalesced unrequested gap bytes.
A proxy coalesces nearby requested spans into economical origin reads: caller slice length excludes coalesced unrequested gap bytes · case 03
A proxy coalesces nearby requested spans into economical origin reads: caller slice length excludes coalesced unrequested gap bytes.
A proxy coalesces nearby requested spans into economical origin reads: caller slice length excludes coalesced unrequested gap bytes · case 04
A proxy coalesces nearby requested spans into economical origin reads: caller slice length excludes coalesced unrequested gap bytes.
A proxy coalesces nearby requested spans into economical origin reads: caller slice length excludes coalesced unrequested gap bytes · case 05
A proxy coalesces nearby requested spans into economical origin reads: caller slice length excludes coalesced unrequested gap bytes.
A proxy coalesces nearby requested spans into economical origin reads: empty selectors retain a null slot in caller mapping · case 01
A proxy coalesces nearby requested spans into economical origin reads: empty selectors retain a null slot in caller mapping.
A proxy coalesces nearby requested spans into economical origin reads: empty selectors retain a null slot in caller mapping · case 02
A proxy coalesces nearby requested spans into economical origin reads: empty selectors retain a null slot in caller mapping.
A proxy coalesces nearby requested spans into economical origin reads: empty selectors retain a null slot in caller mapping · case 03
A proxy coalesces nearby requested spans into economical origin reads: empty selectors retain a null slot in caller mapping.
A proxy coalesces nearby requested spans into economical origin reads: empty selectors retain a null slot in caller mapping · case 04
A proxy coalesces nearby requested spans into economical origin reads: empty selectors retain a null slot in caller mapping.
A proxy coalesces nearby requested spans into economical origin reads: empty selectors retain a null slot in caller mapping · case 05
A proxy coalesces nearby requested spans into economical origin reads: empty selectors retain a null slot in caller mapping.
A bounded Content-Range upload endpoint validates chunk admission: range uploads do not accept retrieval or unframed append methods · case 01
A bounded Content-Range upload endpoint validates chunk admission: range uploads do not accept retrieval or unframed append methods.
A bounded Content-Range upload endpoint validates chunk admission: range uploads do not accept retrieval or unframed append methods · case 02
A bounded Content-Range upload endpoint validates chunk admission: range uploads do not accept retrieval or unframed append methods.
A bounded Content-Range upload endpoint validates chunk admission: range uploads do not accept retrieval or unframed append methods · case 03
A bounded Content-Range upload endpoint validates chunk admission: range uploads do not accept retrieval or unframed append methods.
A bounded Content-Range upload endpoint validates chunk admission: range uploads do not accept retrieval or unframed append methods · case 04
A bounded Content-Range upload endpoint validates chunk admission: range uploads do not accept retrieval or unframed append methods.
A bounded Content-Range upload endpoint validates chunk admission: range uploads do not accept retrieval or unframed append methods · case 05
A bounded Content-Range upload endpoint validates chunk admission: range uploads do not accept retrieval or unframed append methods.
A bounded Content-Range upload endpoint validates chunk admission: a chunk cannot target another upload identifier · case 01
A bounded Content-Range upload endpoint validates chunk admission: a chunk cannot target another upload identifier.
A bounded Content-Range upload endpoint validates chunk admission: a chunk cannot target another upload identifier · case 02
A bounded Content-Range upload endpoint validates chunk admission: a chunk cannot target another upload identifier.
A bounded Content-Range upload endpoint validates chunk admission: a chunk cannot target another upload identifier · case 03
A bounded Content-Range upload endpoint validates chunk admission: a chunk cannot target another upload identifier.
A bounded Content-Range upload endpoint validates chunk admission: a chunk cannot target another upload identifier · case 04
A bounded Content-Range upload endpoint validates chunk admission: a chunk cannot target another upload identifier.
A bounded Content-Range upload endpoint validates chunk admission: a chunk cannot target another upload identifier · case 05
A bounded Content-Range upload endpoint validates chunk admission: a chunk cannot target another upload identifier.
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 ↗