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
An upload status endpoint reports committed byte coverage: the exclusive complete length is not itself a committed byte · case 01
An upload status endpoint reports committed byte coverage: the exclusive complete length is not itself a committed byte.
An upload status endpoint reports committed byte coverage: the exclusive complete length is not itself a committed byte · case 02
An upload status endpoint reports committed byte coverage: the exclusive complete length is not itself a committed byte.
An upload status endpoint reports committed byte coverage: the exclusive complete length is not itself a committed byte · case 03
An upload status endpoint reports committed byte coverage: the exclusive complete length is not itself a committed byte.
An upload status endpoint reports committed byte coverage: the exclusive complete length is not itself a committed byte · case 04
An upload status endpoint reports committed byte coverage: the exclusive complete length is not itself a committed byte.
An upload status endpoint reports committed byte coverage: the exclusive complete length is not itself a committed byte · case 05
An upload status endpoint reports committed byte coverage: the exclusive complete length is not itself a committed byte.
An upload status endpoint reports committed byte coverage: negative offsets cannot appear in acknowledged ranges · case 01
An upload status endpoint reports committed byte coverage: negative offsets cannot appear in acknowledged ranges.
An upload status endpoint reports committed byte coverage: negative offsets cannot appear in acknowledged ranges · case 02
An upload status endpoint reports committed byte coverage: negative offsets cannot appear in acknowledged ranges.
An upload status endpoint reports committed byte coverage: negative offsets cannot appear in acknowledged ranges · case 03
An upload status endpoint reports committed byte coverage: negative offsets cannot appear in acknowledged ranges.
An upload status endpoint reports committed byte coverage: negative offsets cannot appear in acknowledged ranges · case 04
An upload status endpoint reports committed byte coverage: negative offsets cannot appear in acknowledged ranges.
An upload status endpoint reports committed byte coverage: negative offsets cannot appear in acknowledged ranges · case 05
An upload status endpoint reports committed byte coverage: negative offsets cannot appear in acknowledged ranges.
An upload status endpoint reports committed byte coverage: adjacent committed positions extend the current acknowledgement run · case 01
An upload status endpoint reports committed byte coverage: adjacent committed positions extend the current acknowledgement run.
An upload status endpoint reports committed byte coverage: adjacent committed positions extend the current acknowledgement run · case 02
An upload status endpoint reports committed byte coverage: adjacent committed positions extend the current acknowledgement run.
An upload status endpoint reports committed byte coverage: adjacent committed positions extend the current acknowledgement run · case 03
An upload status endpoint reports committed byte coverage: adjacent committed positions extend the current acknowledgement run.
An upload status endpoint reports committed byte coverage: adjacent committed positions extend the current acknowledgement run · case 04
An upload status endpoint reports committed byte coverage: adjacent committed positions extend the current acknowledgement run.
An upload status endpoint reports committed byte coverage: adjacent committed positions extend the current acknowledgement run · case 05
An upload status endpoint reports committed byte coverage: adjacent committed positions extend the current acknowledgement run.
An upload status endpoint reports committed byte coverage: extending a run changes its end while retaining its initial byte · case 01
An upload status endpoint reports committed byte coverage: extending a run changes its end while retaining its initial byte.
An upload status endpoint reports committed byte coverage: extending a run changes its end while retaining its initial byte · case 02
An upload status endpoint reports committed byte coverage: extending a run changes its end while retaining its initial byte.
An upload status endpoint reports committed byte coverage: extending a run changes its end while retaining its initial byte · case 03
An upload status endpoint reports committed byte coverage: extending a run changes its end while retaining its initial byte.
An upload status endpoint reports committed byte coverage: extending a run changes its end while retaining its initial byte · case 04
An upload status endpoint reports committed byte coverage: extending a run changes its end while retaining its initial byte.
An upload status endpoint reports committed byte coverage: extending a run changes its end while retaining its initial byte · case 05
An upload status endpoint reports committed byte coverage: extending a run changes its end while retaining its initial byte.
An upload status endpoint reports committed byte coverage: a new acknowledged run begins at its own first committed byte · case 01
An upload status endpoint reports committed byte coverage: a new acknowledged run begins at its own first committed byte.
An upload status endpoint reports committed byte coverage: a new acknowledged run begins at its own first committed byte · case 02
An upload status endpoint reports committed byte coverage: a new acknowledged run begins at its own first committed byte.
An upload status endpoint reports committed byte coverage: a new acknowledged run begins at its own first committed byte · case 03
An upload status endpoint reports committed byte coverage: a new acknowledged run begins at its own first committed byte.
An upload status endpoint reports committed byte coverage: a new acknowledged run begins at its own first committed byte · case 04
An upload status endpoint reports committed byte coverage: a new acknowledged run begins at its own first committed byte.
An upload status endpoint reports committed byte coverage: a new acknowledged run begins at its own first committed byte · case 05
An upload status endpoint reports committed byte coverage: a new acknowledged run begins at its own first committed byte.
An upload status endpoint reports committed byte coverage: no committed bytes means no acknowledged range field · case 01
An upload status endpoint reports committed byte coverage: no committed bytes means no acknowledged range field.
An upload status endpoint reports committed byte coverage: no committed bytes means no acknowledged range field · case 02
An upload status endpoint reports committed byte coverage: no committed bytes means no acknowledged range field.
An upload status endpoint reports committed byte coverage: no committed bytes means no acknowledged range field · case 03
An upload status endpoint reports committed byte coverage: no committed bytes means no acknowledged range field.
An upload status endpoint reports committed byte coverage: no committed bytes means no acknowledged range field · case 04
An upload status endpoint reports committed byte coverage: no committed bytes means no acknowledged range field.
An upload status endpoint reports committed byte coverage: no committed bytes means no acknowledged range field · case 05
An upload status endpoint reports committed byte coverage: no committed bytes means no acknowledged range field.
An upload status endpoint reports committed byte coverage: the resumable prefix stops at the first byte hole · case 01
An upload status endpoint reports committed byte coverage: the resumable prefix stops at the first byte hole.
An upload status endpoint reports committed byte coverage: the resumable prefix stops at the first byte hole · case 02
An upload status endpoint reports committed byte coverage: the resumable prefix stops at the first byte hole.
An upload status endpoint reports committed byte coverage: the resumable prefix stops at the first byte hole · case 03
An upload status endpoint reports committed byte coverage: the resumable prefix stops at the first byte hole.
An upload status endpoint reports committed byte coverage: the resumable prefix stops at the first byte hole · case 04
An upload status endpoint reports committed byte coverage: the resumable prefix stops at the first byte hole.
An upload status endpoint reports committed byte coverage: the resumable prefix stops at the first byte hole · case 05
An upload status endpoint reports committed byte coverage: the resumable prefix stops at the first byte hole.
An upload status endpoint reports committed byte coverage: zero-length uploads are complete without an acknowledged run · case 01
An upload status endpoint reports committed byte coverage: zero-length uploads are complete without an acknowledged run.
An upload status endpoint reports committed byte coverage: zero-length uploads are complete without an acknowledged run · case 02
An upload status endpoint reports committed byte coverage: zero-length uploads are complete without an acknowledged run.
An upload status endpoint reports committed byte coverage: zero-length uploads are complete without an acknowledged run · case 03
An upload status endpoint reports committed byte coverage: zero-length uploads are complete without an acknowledged run.
An upload status endpoint reports committed byte coverage: zero-length uploads are complete without an acknowledged run · case 04
An upload status endpoint reports committed byte coverage: zero-length uploads are complete without an acknowledged run.
An upload status endpoint reports committed byte coverage: zero-length uploads are complete without an acknowledged run · case 05
An upload status endpoint reports committed byte coverage: zero-length uploads are complete without an acknowledged run.
A row-range endpoint builds byte-addressable line record metadata: the first record starts after the representation BOM bytes · case 01
A row-range endpoint builds byte-addressable line record metadata: the first record starts after the representation BOM bytes.
A row-range endpoint builds byte-addressable line record metadata: the first record starts after the representation BOM bytes · case 02
A row-range endpoint builds byte-addressable line record metadata: the first record starts after the representation BOM bytes.
A row-range endpoint builds byte-addressable line record metadata: the first record starts after the representation BOM bytes · case 03
A row-range endpoint builds byte-addressable line record metadata: the first record starts after the representation BOM bytes.
A row-range endpoint builds byte-addressable line record metadata: the first record starts after the representation BOM bytes · case 04
A row-range endpoint builds byte-addressable line record metadata: the first record starts after the representation BOM bytes.
A row-range endpoint builds byte-addressable line record metadata: the first record starts after the representation BOM bytes · case 05
A row-range endpoint builds byte-addressable line record metadata: the first record starts after the representation BOM bytes.
A row-range endpoint builds byte-addressable line record metadata: a final line without LF remains a selectable record · case 01
A row-range endpoint builds byte-addressable line record metadata: a final line without LF remains a selectable record.
A row-range endpoint builds byte-addressable line record metadata: a final line without LF remains a selectable record · case 02
A row-range endpoint builds byte-addressable line record metadata: a final line without LF remains a selectable record.
A row-range endpoint builds byte-addressable line record metadata: a final line without LF remains a selectable record · case 03
A row-range endpoint builds byte-addressable line record metadata: a final line without LF remains a selectable record.
A row-range endpoint builds byte-addressable line record metadata: a final line without LF remains a selectable record · case 04
A row-range endpoint builds byte-addressable line record metadata: a final line without LF remains a selectable record.
A row-range endpoint builds byte-addressable line record metadata: a final line without LF remains a selectable record · case 05
A row-range endpoint builds byte-addressable line record metadata: a final line without LF remains a selectable record.
A row-range endpoint builds byte-addressable line record metadata: CR in a CRLF terminator is not part of the row payload · case 01
A row-range endpoint builds byte-addressable line record metadata: CR in a CRLF terminator is not part of the row payload.
A row-range endpoint builds byte-addressable line record metadata: CR in a CRLF terminator is not part of the row payload · case 02
A row-range endpoint builds byte-addressable line record metadata: CR in a CRLF terminator is not part of the row payload.
A row-range endpoint builds byte-addressable line record metadata: CR in a CRLF terminator is not part of the row payload · case 03
A row-range endpoint builds byte-addressable line record metadata: CR in a CRLF terminator is not part of the row payload.
A row-range endpoint builds byte-addressable line record metadata: CR in a CRLF terminator is not part of the row payload · case 04
A row-range endpoint builds byte-addressable line record metadata: CR in a CRLF terminator is not part of the row payload.
A row-range endpoint builds byte-addressable line record metadata: CR in a CRLF terminator is not part of the row payload · case 05
A row-range endpoint builds byte-addressable line record metadata: CR in a CRLF terminator is not part of the row payload.
A row-range endpoint builds byte-addressable line record metadata: CRLF consumes two physical representation bytes · case 01
A row-range endpoint builds byte-addressable line record metadata: CRLF consumes two physical representation bytes.
A row-range endpoint builds byte-addressable line record metadata: CRLF consumes two physical representation bytes · case 02
A row-range endpoint builds byte-addressable line record metadata: CRLF consumes two physical representation bytes.
A row-range endpoint builds byte-addressable line record metadata: CRLF consumes two physical representation bytes · case 03
A row-range endpoint builds byte-addressable line record metadata: CRLF consumes two physical representation bytes.
A row-range endpoint builds byte-addressable line record metadata: CRLF consumes two physical representation bytes · case 04
A row-range endpoint builds byte-addressable line record metadata: CRLF consumes two physical representation bytes.
A row-range endpoint builds byte-addressable line record metadata: CRLF consumes two physical representation bytes · case 05
A row-range endpoint builds byte-addressable line record metadata: CRLF consumes two physical representation bytes.
A row-range endpoint builds byte-addressable line record metadata: empty line separators do not allocate logical record numbers · case 01
A row-range endpoint builds byte-addressable line record metadata: empty line separators do not allocate logical record numbers.
A row-range endpoint builds byte-addressable line record metadata: empty line separators do not allocate logical record numbers · case 02
A row-range endpoint builds byte-addressable line record metadata: empty line separators do not allocate logical record numbers.
A row-range endpoint builds byte-addressable line record metadata: empty line separators do not allocate logical record numbers · case 03
A row-range endpoint builds byte-addressable line record metadata: empty line separators do not allocate logical record numbers.
A row-range endpoint builds byte-addressable line record metadata: empty line separators do not allocate logical record numbers · case 04
A row-range endpoint builds byte-addressable line record metadata: empty line separators do not allocate logical record numbers.
A row-range endpoint builds byte-addressable line record metadata: empty line separators do not allocate logical record numbers · case 05
A row-range endpoint builds byte-addressable line record metadata: empty line separators do not allocate logical record numbers.
A row-range endpoint builds byte-addressable line record metadata: multibyte record contents count toward the byte-index cap · case 01
A row-range endpoint builds byte-addressable line record metadata: multibyte record contents count toward the byte-index cap.
A row-range endpoint builds byte-addressable line record metadata: multibyte record contents count toward the byte-index cap · case 02
A row-range endpoint builds byte-addressable line record metadata: multibyte record contents count toward the byte-index cap.
A row-range endpoint builds byte-addressable line record metadata: multibyte record contents count toward the byte-index cap · case 03
A row-range endpoint builds byte-addressable line record metadata: multibyte record contents count toward the byte-index cap.
A row-range endpoint builds byte-addressable line record metadata: multibyte record contents count toward the byte-index cap · case 04
A row-range endpoint builds byte-addressable line record metadata: multibyte record contents count toward the byte-index cap.
A row-range endpoint builds byte-addressable line record metadata: multibyte record contents count toward the byte-index cap · case 05
A row-range endpoint builds byte-addressable line record metadata: multibyte record contents count toward the byte-index cap.
A row-range endpoint builds byte-addressable line record metadata: index entries expose octet counts rather than codepoint counts · case 01
A row-range endpoint builds byte-addressable line record metadata: index entries expose octet counts rather than codepoint counts.
A row-range endpoint builds byte-addressable line record metadata: index entries expose octet counts rather than codepoint counts · case 02
A row-range endpoint builds byte-addressable line record metadata: index entries expose octet counts rather than codepoint counts.
A row-range endpoint builds byte-addressable line record metadata: index entries expose octet counts rather than codepoint counts · case 03
A row-range endpoint builds byte-addressable line record metadata: index entries expose octet counts rather than codepoint counts.
A row-range endpoint builds byte-addressable line record metadata: index entries expose octet counts rather than codepoint counts · case 04
A row-range endpoint builds byte-addressable line record metadata: index entries expose octet counts rather than codepoint counts.
A row-range endpoint builds byte-addressable line record metadata: index entries expose octet counts rather than codepoint counts · case 05
A row-range endpoint builds byte-addressable line record metadata: index entries expose octet counts rather than codepoint counts.
A row-range endpoint builds byte-addressable line record metadata: physical row scanning advances past the complete line terminator · case 01
A row-range endpoint builds byte-addressable line record metadata: physical row scanning advances past the complete line terminator.
A row-range endpoint builds byte-addressable line record metadata: physical row scanning advances past the complete line terminator · case 02
A row-range endpoint builds byte-addressable line record metadata: physical row scanning advances past the complete line terminator.
A row-range endpoint builds byte-addressable line record metadata: physical row scanning advances past the complete line terminator · case 03
A row-range endpoint builds byte-addressable line record metadata: physical row scanning advances past the complete line terminator.
A row-range endpoint builds byte-addressable line record metadata: physical row scanning advances past the complete line terminator · case 04
A row-range endpoint builds byte-addressable line record metadata: physical row scanning advances past the complete line terminator.
A row-range endpoint builds byte-addressable line record metadata: physical row scanning advances past the complete line terminator · case 05
A row-range endpoint builds byte-addressable line record metadata: physical row scanning advances past the complete line terminator.
A row-range endpoint builds byte-addressable line record metadata: negative row indices are invalid rather than Python tail indexing · case 01
A row-range endpoint builds byte-addressable line record metadata: negative row indices are invalid rather than Python tail indexing.
A row-range endpoint builds byte-addressable line record metadata: negative row indices are invalid rather than Python tail indexing · case 02
A row-range endpoint builds byte-addressable line record metadata: negative row indices are invalid rather than Python tail indexing.
A row-range endpoint builds byte-addressable line record metadata: negative row indices are invalid rather than Python tail indexing · case 03
A row-range endpoint builds byte-addressable line record metadata: negative row indices are invalid rather than Python tail indexing.
A row-range endpoint builds byte-addressable line record metadata: negative row indices are invalid rather than Python tail indexing · case 04
A row-range endpoint builds byte-addressable line record metadata: negative row indices are invalid rather than Python tail indexing.
A row-range endpoint builds byte-addressable line record metadata: negative row indices are invalid rather than Python tail indexing · case 05
A row-range endpoint builds byte-addressable line record metadata: negative row indices are invalid rather than Python tail indexing.
A row-range endpoint builds byte-addressable line record metadata: repeat row selectors retain repeated response bodies · case 01
A row-range endpoint builds byte-addressable line record metadata: repeat row selectors retain repeated response bodies.
A row-range endpoint builds byte-addressable line record metadata: repeat row selectors retain repeated response bodies · case 02
A row-range endpoint builds byte-addressable line record metadata: repeat row selectors retain repeated response bodies.
A row-range endpoint builds byte-addressable line record metadata: repeat row selectors retain repeated response bodies · case 03
A row-range endpoint builds byte-addressable line record metadata: repeat row selectors retain repeated response bodies.
A row-range endpoint builds byte-addressable line record metadata: repeat row selectors retain repeated response bodies · case 04
A row-range endpoint builds byte-addressable line record metadata: repeat row selectors retain repeated response bodies.
A row-range endpoint builds byte-addressable line record metadata: repeat row selectors retain repeated response bodies · case 05
A row-range endpoint builds byte-addressable line record metadata: repeat row selectors retain repeated response bodies.
A zero-copy range sender accounts for partial progress reported with syscall errors: late syscall completions do not reopen completed range streams · case 01
A zero-copy range sender accounts for partial progress reported with syscall errors: late syscall completions do not reopen completed range streams.
A zero-copy range sender accounts for partial progress reported with syscall errors: late syscall completions do not reopen completed range streams · case 02
A zero-copy range sender accounts for partial progress reported with syscall errors: late syscall completions do not reopen completed range streams.
A zero-copy range sender accounts for partial progress reported with syscall errors: late syscall completions do not reopen completed range streams · case 03
A zero-copy range sender accounts for partial progress reported with syscall errors: late syscall completions do not reopen completed range streams.
A zero-copy range sender accounts for partial progress reported with syscall errors: late syscall completions do not reopen completed range streams · case 04
A zero-copy range sender accounts for partial progress reported with syscall errors: late syscall completions do not reopen completed range streams.
A zero-copy range sender accounts for partial progress reported with syscall errors: late syscall completions do not reopen completed range streams · case 05
A zero-copy range sender accounts for partial progress reported with syscall errors: late syscall completions do not reopen completed range streams.
A zero-copy range sender accounts for partial progress reported with syscall errors: invalid negative syscall counts cannot rewind a range cursor · case 01
A zero-copy range sender accounts for partial progress reported with syscall errors: invalid negative syscall counts cannot rewind a range cursor.
A zero-copy range sender accounts for partial progress reported with syscall errors: invalid negative syscall counts cannot rewind a range cursor · case 02
A zero-copy range sender accounts for partial progress reported with syscall errors: invalid negative syscall counts cannot rewind a range cursor.
A zero-copy range sender accounts for partial progress reported with syscall errors: invalid negative syscall counts cannot rewind a range cursor · case 03
A zero-copy range sender accounts for partial progress reported with syscall errors: invalid negative syscall counts cannot rewind a range cursor.
A zero-copy range sender accounts for partial progress reported with syscall errors: invalid negative syscall counts cannot rewind a range cursor · case 04
A zero-copy range sender accounts for partial progress reported with syscall errors: invalid negative syscall counts cannot rewind a range cursor.
A zero-copy range sender accounts for partial progress reported with syscall errors: invalid negative syscall counts cannot rewind a range cursor · case 05
A zero-copy range sender accounts for partial progress reported with syscall errors: invalid negative syscall counts cannot rewind a range cursor.
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 ↗