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 longer boundary prefix is not mistaken for the chosen delimiter · case 01
A longer boundary prefix is not mistaken for the chosen delimiter.
A longer boundary prefix is not mistaken for the chosen delimiter · case 02
A longer boundary prefix is not mistaken for the chosen delimiter.
A longer boundary prefix is not mistaken for the chosen delimiter · case 03
A longer boundary prefix is not mistaken for the chosen delimiter.
A longer boundary prefix is not mistaken for the chosen delimiter · case 04
A longer boundary prefix is not mistaken for the chosen delimiter.
A longer boundary prefix is not mistaken for the chosen delimiter · case 05
A longer boundary prefix is not mistaken for the chosen delimiter.
Part headers end at the first double CRLF · case 01
Part headers end at the first double CRLF.
Part headers end at the first double CRLF · case 02
Part headers end at the first double CRLF.
Part headers end at the first double CRLF · case 03
Part headers end at the first double CRLF.
Part headers end at the first double CRLF · case 04
Part headers end at the first double CRLF.
Part headers end at the first double CRLF · case 05
Part headers end at the first double CRLF.
Part header lookup normalizes names without rewriting values · case 01
Part header lookup normalizes names without rewriting values.
Part header lookup normalizes names without rewriting values · case 02
Part header lookup normalizes names without rewriting values.
Part header lookup normalizes names without rewriting values · case 03
Part header lookup normalizes names without rewriting values.
Part header lookup normalizes names without rewriting values · case 04
Part header lookup normalizes names without rewriting values.
Part header lookup normalizes names without rewriting values · case 05
Part header lookup normalizes names without rewriting values.
Each received part needs its own explicit range metadata · case 01
Each received part needs its own explicit range metadata.
Each received part needs its own explicit range metadata · case 02
Each received part needs its own explicit range metadata.
Each received part needs its own explicit range metadata · case 03
Each received part needs its own explicit range metadata.
Each received part needs its own explicit range metadata · case 04
Each received part needs its own explicit range metadata.
Each received part needs its own explicit range metadata · case 05
Each received part needs its own explicit range metadata.
End-of-stream without a closing delimiter leaves the response incomplete · case 01
End-of-stream without a closing delimiter leaves the response incomplete.
End-of-stream without a closing delimiter leaves the response incomplete · case 02
End-of-stream without a closing delimiter leaves the response incomplete.
End-of-stream without a closing delimiter leaves the response incomplete · case 03
End-of-stream without a closing delimiter leaves the response incomplete.
End-of-stream without a closing delimiter leaves the response incomplete · case 04
End-of-stream without a closing delimiter leaves the response incomplete.
End-of-stream without a closing delimiter leaves the response incomplete · case 05
End-of-stream without a closing delimiter leaves the response incomplete.
Bytes after the closing delimiter do not enter the last range body · case 01
Bytes after the closing delimiter do not enter the last range body.
Bytes after the closing delimiter do not enter the last range body · case 02
Bytes after the closing delimiter do not enter the last range body.
Bytes after the closing delimiter do not enter the last range body · case 03
Bytes after the closing delimiter do not enter the last range body.
Bytes after the closing delimiter do not enter the last range body · case 04
Bytes after the closing delimiter do not enter the last range body.
Bytes after the closing delimiter do not enter the last range body · case 05
Bytes after the closing delimiter do not enter the last range body.
Preamble bytes before the first delimiter do not form a range part · case 01
Preamble bytes before the first delimiter do not form a range part.
Preamble bytes before the first delimiter do not form a range part · case 02
Preamble bytes before the first delimiter do not form a range part.
Preamble bytes before the first delimiter do not form a range part · case 03
Preamble bytes before the first delimiter do not form a range part.
Preamble bytes before the first delimiter do not form a range part · case 04
Preamble bytes before the first delimiter do not form a range part.
Preamble bytes before the first delimiter do not form a range part · case 05
Preamble bytes before the first delimiter do not form a range part.
Range body whitespace remains byte-exact after framing removal · case 01
Range body whitespace remains byte-exact after framing removal.
Range body whitespace remains byte-exact after framing removal · case 02
Range body whitespace remains byte-exact after framing removal.
Range body whitespace remains byte-exact after framing removal · case 03
Range body whitespace remains byte-exact after framing removal.
Range body whitespace remains byte-exact after framing removal · case 04
Range body whitespace remains byte-exact after framing removal.
Range body whitespace remains byte-exact after framing removal · case 05
Range body whitespace remains byte-exact after framing removal.
Multipart boundary parameter parsing: quoted separator bytes stay inside the boundary · case 01
Multipart boundary parameter parsing: quoted separator bytes stay inside the boundary.
Multipart boundary parameter parsing: quoted separator bytes stay inside the boundary · case 02
Multipart boundary parameter parsing: quoted separator bytes stay inside the boundary.
Multipart boundary parameter parsing: quoted separator bytes stay inside the boundary · case 03
Multipart boundary parameter parsing: quoted separator bytes stay inside the boundary.
Multipart boundary parameter parsing: quoted separator bytes stay inside the boundary · case 04
Multipart boundary parameter parsing: quoted separator bytes stay inside the boundary.
Multipart boundary parameter parsing: quoted separator bytes stay inside the boundary · case 05
Multipart boundary parameter parsing: quoted separator bytes stay inside the boundary.
Multipart boundary parameter parsing: quoted escapes preserve the escaped character · case 01
Multipart boundary parameter parsing: quoted escapes preserve the escaped character.
Multipart boundary parameter parsing: quoted escapes preserve the escaped character · case 02
Multipart boundary parameter parsing: quoted escapes preserve the escaped character.
Multipart boundary parameter parsing: quoted escapes preserve the escaped character · case 03
Multipart boundary parameter parsing: quoted escapes preserve the escaped character.
Multipart boundary parameter parsing: quoted escapes preserve the escaped character · case 04
Multipart boundary parameter parsing: quoted escapes preserve the escaped character.
Multipart boundary parameter parsing: quoted escapes preserve the escaped character · case 05
Multipart boundary parameter parsing: quoted escapes preserve the escaped character.
Multipart boundary parameter parsing: closing quotes exit quoted parameter state · case 01
Multipart boundary parameter parsing: closing quotes exit quoted parameter state.
Multipart boundary parameter parsing: closing quotes exit quoted parameter state · case 02
Multipart boundary parameter parsing: closing quotes exit quoted parameter state.
Multipart boundary parameter parsing: closing quotes exit quoted parameter state · case 03
Multipart boundary parameter parsing: closing quotes exit quoted parameter state.
Multipart boundary parameter parsing: closing quotes exit quoted parameter state · case 04
Multipart boundary parameter parsing: closing quotes exit quoted parameter state.
Multipart boundary parameter parsing: closing quotes exit quoted parameter state · case 05
Multipart boundary parameter parsing: closing quotes exit quoted parameter state.
Multipart boundary parameter parsing: incomplete quoted boundaries are rejected · case 01
Multipart boundary parameter parsing: incomplete quoted boundaries are rejected.
Multipart boundary parameter parsing: incomplete quoted boundaries are rejected · case 02
Multipart boundary parameter parsing: incomplete quoted boundaries are rejected.
Multipart boundary parameter parsing: incomplete quoted boundaries are rejected · case 03
Multipart boundary parameter parsing: incomplete quoted boundaries are rejected.
Multipart boundary parameter parsing: incomplete quoted boundaries are rejected · case 04
Multipart boundary parameter parsing: incomplete quoted boundaries are rejected.
Multipart boundary parameter parsing: incomplete quoted boundaries are rejected · case 05
Multipart boundary parameter parsing: incomplete quoted boundaries are rejected.
Multipart boundary parameter parsing: boundary parameter names are normalized independently of values · case 01
Multipart boundary parameter parsing: boundary parameter names are normalized independently of values.
Multipart boundary parameter parsing: boundary parameter names are normalized independently of values · case 02
Multipart boundary parameter parsing: boundary parameter names are normalized independently of values.
Multipart boundary parameter parsing: boundary parameter names are normalized independently of values · case 03
Multipart boundary parameter parsing: boundary parameter names are normalized independently of values.
Multipart boundary parameter parsing: boundary parameter names are normalized independently of values · case 04
Multipart boundary parameter parsing: boundary parameter names are normalized independently of values.
Multipart boundary parameter parsing: boundary parameter names are normalized independently of values · case 05
Multipart boundary parameter parsing: boundary parameter names are normalized independently of values.
Multipart boundary parameter parsing: duplicate boundary declarations remain ambiguous even when identical · case 01
Multipart boundary parameter parsing: duplicate boundary declarations remain ambiguous even when identical.
Multipart boundary parameter parsing: duplicate boundary declarations remain ambiguous even when identical · case 02
Multipart boundary parameter parsing: duplicate boundary declarations remain ambiguous even when identical.
Multipart boundary parameter parsing: duplicate boundary declarations remain ambiguous even when identical · case 03
Multipart boundary parameter parsing: duplicate boundary declarations remain ambiguous even when identical.
Multipart boundary parameter parsing: duplicate boundary declarations remain ambiguous even when identical · case 04
Multipart boundary parameter parsing: duplicate boundary declarations remain ambiguous even when identical.
Multipart boundary parameter parsing: duplicate boundary declarations remain ambiguous even when identical · case 05
Multipart boundary parameter parsing: duplicate boundary declarations remain ambiguous even when identical.
Multipart boundary parameter parsing: a mixed multipart body is not accepted as a byte range body · case 01
Multipart boundary parameter parsing: a mixed multipart body is not accepted as a byte range body.
Multipart boundary parameter parsing: a mixed multipart body is not accepted as a byte range body · case 02
Multipart boundary parameter parsing: a mixed multipart body is not accepted as a byte range body.
Multipart boundary parameter parsing: a mixed multipart body is not accepted as a byte range body · case 03
Multipart boundary parameter parsing: a mixed multipart body is not accepted as a byte range body.
Multipart boundary parameter parsing: a mixed multipart body is not accepted as a byte range body · case 04
Multipart boundary parameter parsing: a mixed multipart body is not accepted as a byte range body.
Multipart boundary parameter parsing: a mixed multipart body is not accepted as a byte range body · case 05
Multipart boundary parameter parsing: a mixed multipart body is not accepted as a byte range body.
Multipart boundary parameter parsing: zero-length boundary strings cannot delimit parts · case 01
Multipart boundary parameter parsing: zero-length boundary strings cannot delimit parts.
Multipart boundary parameter parsing: zero-length boundary strings cannot delimit parts · case 02
Multipart boundary parameter parsing: zero-length boundary strings cannot delimit parts.
Multipart boundary parameter parsing: zero-length boundary strings cannot delimit parts · case 03
Multipart boundary parameter parsing: zero-length boundary strings cannot delimit parts.
Multipart boundary parameter parsing: zero-length boundary strings cannot delimit parts · case 04
Multipart boundary parameter parsing: zero-length boundary strings cannot delimit parts.
Multipart boundary parameter parsing: zero-length boundary strings cannot delimit parts · case 05
Multipart boundary parameter parsing: zero-length boundary strings cannot delimit parts.
Multipart boundary parameter parsing: the local boundary cap counts decoded delimiter characters · case 01
Multipart boundary parameter parsing: the local boundary cap counts decoded delimiter characters.
Multipart boundary parameter parsing: the local boundary cap counts decoded delimiter characters · case 02
Multipart boundary parameter parsing: the local boundary cap counts decoded delimiter characters.
Multipart boundary parameter parsing: the local boundary cap counts decoded delimiter characters · case 03
Multipart boundary parameter parsing: the local boundary cap counts decoded delimiter characters.
Multipart boundary parameter parsing: the local boundary cap counts decoded delimiter characters · case 04
Multipart boundary parameter parsing: the local boundary cap counts decoded delimiter characters.
Multipart boundary parameter parsing: the local boundary cap counts decoded delimiter characters · case 05
Multipart boundary parameter parsing: the local boundary cap counts decoded delimiter characters.
Multipart boundary parameter parsing: all control bytes are excluded from the delimiter · case 01
Multipart boundary parameter parsing: all control bytes are excluded from the delimiter.
Multipart boundary parameter parsing: all control bytes are excluded from the delimiter · case 02
Multipart boundary parameter parsing: all control bytes are excluded from the delimiter.
Multipart boundary parameter parsing: all control bytes are excluded from the delimiter · case 03
Multipart boundary parameter parsing: all control bytes are excluded from the delimiter.
Multipart boundary parameter parsing: all control bytes are excluded from the delimiter · case 04
Multipart boundary parameter parsing: all control bytes are excluded from the delimiter.
Multipart boundary parameter parsing: all control bytes are excluded from the delimiter · case 05
Multipart boundary parameter parsing: all control bytes are excluded from the delimiter.
A packed-object origin maps logical byte requests to immutable backing objects: logical placement uses extent logical base rather than pack offset · case 01
A packed-object origin maps logical byte requests to immutable backing objects: logical placement uses extent logical base rather than pack offset.
A packed-object origin maps logical byte requests to immutable backing objects: logical placement uses extent logical base rather than pack offset · case 02
A packed-object origin maps logical byte requests to immutable backing objects: logical placement uses extent logical base rather than pack offset.
A packed-object origin maps logical byte requests to immutable backing objects: logical placement uses extent logical base rather than pack offset · case 03
A packed-object origin maps logical byte requests to immutable backing objects: logical placement uses extent logical base rather than pack offset.
A packed-object origin maps logical byte requests to immutable backing objects: logical placement uses extent logical base rather than pack offset · case 04
A packed-object origin maps logical byte requests to immutable backing objects: logical placement uses extent logical base rather than pack offset.
A packed-object origin maps logical byte requests to immutable backing objects: logical placement uses extent logical base rather than pack offset · case 05
A packed-object origin maps logical byte requests to immutable backing objects: logical placement uses extent logical base rather than pack offset.
A packed-object origin maps logical byte requests to immutable backing objects: backing reads include the physical prefix within each pack · case 01
A packed-object origin maps logical byte requests to immutable backing objects: backing reads include the physical prefix within each pack.
A packed-object origin maps logical byte requests to immutable backing objects: backing reads include the physical prefix within each pack · case 02
A packed-object origin maps logical byte requests to immutable backing objects: backing reads include the physical prefix within each pack.
A packed-object origin maps logical byte requests to immutable backing objects: backing reads include the physical prefix within each pack · case 03
A packed-object origin maps logical byte requests to immutable backing objects: backing reads include the physical prefix within each pack.
A packed-object origin maps logical byte requests to immutable backing objects: backing reads include the physical prefix within each pack · case 04
A packed-object origin maps logical byte requests to immutable backing objects: backing reads include the physical prefix within each pack.
A packed-object origin maps logical byte requests to immutable backing objects: backing reads include the physical prefix within each pack · case 05
A packed-object origin maps logical byte requests to immutable backing objects: backing reads include the physical prefix within each pack.
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 ↗