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 bounded Content-Range upload endpoint validates chunk admission: future as well as stale generations require a new session plan · case 01
A bounded Content-Range upload endpoint validates chunk admission: future as well as stale generations require a new session plan.
A bounded Content-Range upload endpoint validates chunk admission: future as well as stale generations require a new session plan · case 02
A bounded Content-Range upload endpoint validates chunk admission: future as well as stale generations require a new session plan.
A bounded Content-Range upload endpoint validates chunk admission: future as well as stale generations require a new session plan · case 03
A bounded Content-Range upload endpoint validates chunk admission: future as well as stale generations require a new session plan.
A bounded Content-Range upload endpoint validates chunk admission: future as well as stale generations require a new session plan · case 04
A bounded Content-Range upload endpoint validates chunk admission: future as well as stale generations require a new session plan.
A bounded Content-Range upload endpoint validates chunk admission: future as well as stale generations require a new session plan · case 05
A bounded Content-Range upload endpoint validates chunk admission: future as well as stale generations require a new session plan.
A bounded Content-Range upload endpoint validates chunk admission: chunks cannot silently revise session representation length · case 01
A bounded Content-Range upload endpoint validates chunk admission: chunks cannot silently revise session representation length.
A bounded Content-Range upload endpoint validates chunk admission: chunks cannot silently revise session representation length · case 02
A bounded Content-Range upload endpoint validates chunk admission: chunks cannot silently revise session representation length.
A bounded Content-Range upload endpoint validates chunk admission: chunks cannot silently revise session representation length · case 03
A bounded Content-Range upload endpoint validates chunk admission: chunks cannot silently revise session representation length.
A bounded Content-Range upload endpoint validates chunk admission: chunks cannot silently revise session representation length · case 04
A bounded Content-Range upload endpoint validates chunk admission: chunks cannot silently revise session representation length.
A bounded Content-Range upload endpoint validates chunk admission: chunks cannot silently revise session representation length · case 05
A bounded Content-Range upload endpoint validates chunk admission: chunks cannot silently revise session representation length.
A bounded Content-Range upload endpoint validates chunk admission: small chunks cannot evade the complete-object storage quota · case 01
A bounded Content-Range upload endpoint validates chunk admission: small chunks cannot evade the complete-object storage quota.
A bounded Content-Range upload endpoint validates chunk admission: small chunks cannot evade the complete-object storage quota · case 02
A bounded Content-Range upload endpoint validates chunk admission: small chunks cannot evade the complete-object storage quota.
A bounded Content-Range upload endpoint validates chunk admission: small chunks cannot evade the complete-object storage quota · case 03
A bounded Content-Range upload endpoint validates chunk admission: small chunks cannot evade the complete-object storage quota.
A bounded Content-Range upload endpoint validates chunk admission: small chunks cannot evade the complete-object storage quota · case 04
A bounded Content-Range upload endpoint validates chunk admission: small chunks cannot evade the complete-object storage quota.
A bounded Content-Range upload endpoint validates chunk admission: small chunks cannot evade the complete-object storage quota · case 05
A bounded Content-Range upload endpoint validates chunk admission: small chunks cannot evade the complete-object storage quota.
A bounded Content-Range upload endpoint validates chunk admission: negative upload coordinates cannot address the end of storage · case 01
A bounded Content-Range upload endpoint validates chunk admission: negative upload coordinates cannot address the end of storage.
A bounded Content-Range upload endpoint validates chunk admission: negative upload coordinates cannot address the end of storage · case 02
A bounded Content-Range upload endpoint validates chunk admission: negative upload coordinates cannot address the end of storage.
A bounded Content-Range upload endpoint validates chunk admission: negative upload coordinates cannot address the end of storage · case 03
A bounded Content-Range upload endpoint validates chunk admission: negative upload coordinates cannot address the end of storage.
A bounded Content-Range upload endpoint validates chunk admission: negative upload coordinates cannot address the end of storage · case 04
A bounded Content-Range upload endpoint validates chunk admission: negative upload coordinates cannot address the end of storage.
A bounded Content-Range upload endpoint validates chunk admission: negative upload coordinates cannot address the end of storage · case 05
A bounded Content-Range upload endpoint validates chunk admission: negative upload coordinates cannot address the end of storage.
A bounded Content-Range upload endpoint validates chunk admission: declared byte coverage is not trusted beyond received body length · case 01
A bounded Content-Range upload endpoint validates chunk admission: declared byte coverage is not trusted beyond received body length.
A bounded Content-Range upload endpoint validates chunk admission: declared byte coverage is not trusted beyond received body length · case 02
A bounded Content-Range upload endpoint validates chunk admission: declared byte coverage is not trusted beyond received body length.
A bounded Content-Range upload endpoint validates chunk admission: declared byte coverage is not trusted beyond received body length · case 03
A bounded Content-Range upload endpoint validates chunk admission: declared byte coverage is not trusted beyond received body length.
A bounded Content-Range upload endpoint validates chunk admission: declared byte coverage is not trusted beyond received body length · case 04
A bounded Content-Range upload endpoint validates chunk admission: declared byte coverage is not trusted beyond received body length.
A bounded Content-Range upload endpoint validates chunk admission: declared byte coverage is not trusted beyond received body length · case 05
A bounded Content-Range upload endpoint validates chunk admission: declared byte coverage is not trusted beyond received body length.
A bounded Content-Range upload endpoint validates chunk admission: identical retransmission is allowed while conflicting bytes are rejected · case 01
A bounded Content-Range upload endpoint validates chunk admission: identical retransmission is allowed while conflicting bytes are rejected.
A bounded Content-Range upload endpoint validates chunk admission: identical retransmission is allowed while conflicting bytes are rejected · case 02
A bounded Content-Range upload endpoint validates chunk admission: identical retransmission is allowed while conflicting bytes are rejected.
A bounded Content-Range upload endpoint validates chunk admission: identical retransmission is allowed while conflicting bytes are rejected · case 03
A bounded Content-Range upload endpoint validates chunk admission: identical retransmission is allowed while conflicting bytes are rejected.
A bounded Content-Range upload endpoint validates chunk admission: identical retransmission is allowed while conflicting bytes are rejected · case 04
A bounded Content-Range upload endpoint validates chunk admission: identical retransmission is allowed while conflicting bytes are rejected.
A bounded Content-Range upload endpoint validates chunk admission: identical retransmission is allowed while conflicting bytes are rejected · case 05
A bounded Content-Range upload endpoint validates chunk admission: identical retransmission is allowed while conflicting bytes are rejected.
A bounded Content-Range upload endpoint validates chunk admission: admitted upload chunks write at declared absolute offsets · case 01
A bounded Content-Range upload endpoint validates chunk admission: admitted upload chunks write at declared absolute offsets.
A bounded Content-Range upload endpoint validates chunk admission: admitted upload chunks write at declared absolute offsets · case 02
A bounded Content-Range upload endpoint validates chunk admission: admitted upload chunks write at declared absolute offsets.
A bounded Content-Range upload endpoint validates chunk admission: admitted upload chunks write at declared absolute offsets · case 03
A bounded Content-Range upload endpoint validates chunk admission: admitted upload chunks write at declared absolute offsets.
A bounded Content-Range upload endpoint validates chunk admission: admitted upload chunks write at declared absolute offsets · case 04
A bounded Content-Range upload endpoint validates chunk admission: admitted upload chunks write at declared absolute offsets.
A bounded Content-Range upload endpoint validates chunk admission: admitted upload chunks write at declared absolute offsets · case 05
A bounded Content-Range upload endpoint validates chunk admission: admitted upload chunks write at declared absolute offsets.
A bounded Content-Range upload endpoint validates chunk admission: a nonempty accepted chunk is not necessarily a complete upload · case 01
A bounded Content-Range upload endpoint validates chunk admission: a nonempty accepted chunk is not necessarily a complete upload.
A bounded Content-Range upload endpoint validates chunk admission: a nonempty accepted chunk is not necessarily a complete upload · case 02
A bounded Content-Range upload endpoint validates chunk admission: a nonempty accepted chunk is not necessarily a complete upload.
A bounded Content-Range upload endpoint validates chunk admission: a nonempty accepted chunk is not necessarily a complete upload · case 03
A bounded Content-Range upload endpoint validates chunk admission: a nonempty accepted chunk is not necessarily a complete upload.
A bounded Content-Range upload endpoint validates chunk admission: a nonempty accepted chunk is not necessarily a complete upload · case 04
A bounded Content-Range upload endpoint validates chunk admission: a nonempty accepted chunk is not necessarily a complete upload.
A bounded Content-Range upload endpoint validates chunk admission: a nonempty accepted chunk is not necessarily a complete upload · case 05
A bounded Content-Range upload endpoint validates chunk admission: a nonempty accepted chunk is not necessarily a complete upload.
A multipart sender resumes framing and payload segments across transport credit windows: finishing a segment advances exactly one framing component · case 01
A multipart sender resumes framing and payload segments across transport credit windows: finishing a segment advances exactly one framing component.
A multipart sender resumes framing and payload segments across transport credit windows: finishing a segment advances exactly one framing component · case 02
A multipart sender resumes framing and payload segments across transport credit windows: finishing a segment advances exactly one framing component.
A multipart sender resumes framing and payload segments across transport credit windows: finishing a segment advances exactly one framing component · case 03
A multipart sender resumes framing and payload segments across transport credit windows: finishing a segment advances exactly one framing component.
A multipart sender resumes framing and payload segments across transport credit windows: finishing a segment advances exactly one framing component · case 04
A multipart sender resumes framing and payload segments across transport credit windows: finishing a segment advances exactly one framing component.
A multipart sender resumes framing and payload segments across transport credit windows: finishing a segment advances exactly one framing component · case 05
A multipart sender resumes framing and payload segments across transport credit windows: finishing a segment advances exactly one framing component.
A multipart sender resumes framing and payload segments across transport credit windows: a new framing component starts at its own zero offset · case 01
A multipart sender resumes framing and payload segments across transport credit windows: a new framing component starts at its own zero offset.
A multipart sender resumes framing and payload segments across transport credit windows: a new framing component starts at its own zero offset · case 02
A multipart sender resumes framing and payload segments across transport credit windows: a new framing component starts at its own zero offset.
A multipart sender resumes framing and payload segments across transport credit windows: a new framing component starts at its own zero offset · case 03
A multipart sender resumes framing and payload segments across transport credit windows: a new framing component starts at its own zero offset.
A multipart sender resumes framing and payload segments across transport credit windows: a new framing component starts at its own zero offset · case 04
A multipart sender resumes framing and payload segments across transport credit windows: a new framing component starts at its own zero offset.
A multipart sender resumes framing and payload segments across transport credit windows: a new framing component starts at its own zero offset · case 05
A multipart sender resumes framing and payload segments across transport credit windows: a new framing component starts at its own zero offset.
A multipart sender resumes framing and payload segments across transport credit windows: zero transport credit cannot emit a pending delimiter byte · case 01
A multipart sender resumes framing and payload segments across transport credit windows: zero transport credit cannot emit a pending delimiter byte.
A multipart sender resumes framing and payload segments across transport credit windows: zero transport credit cannot emit a pending delimiter byte · case 02
A multipart sender resumes framing and payload segments across transport credit windows: zero transport credit cannot emit a pending delimiter byte.
A multipart sender resumes framing and payload segments across transport credit windows: zero transport credit cannot emit a pending delimiter byte · case 03
A multipart sender resumes framing and payload segments across transport credit windows: zero transport credit cannot emit a pending delimiter byte.
A multipart sender resumes framing and payload segments across transport credit windows: zero transport credit cannot emit a pending delimiter byte · case 04
A multipart sender resumes framing and payload segments across transport credit windows: zero transport credit cannot emit a pending delimiter byte.
A multipart sender resumes framing and payload segments across transport credit windows: zero transport credit cannot emit a pending delimiter byte · case 05
A multipart sender resumes framing and payload segments across transport credit windows: zero transport credit cannot emit a pending delimiter byte.
A multipart sender resumes framing and payload segments across transport credit windows: drain size considers the remaining suffix instead of whole segment length · case 01
A multipart sender resumes framing and payload segments across transport credit windows: drain size considers the remaining suffix instead of whole segment length.
A multipart sender resumes framing and payload segments across transport credit windows: drain size considers the remaining suffix instead of whole segment length · case 02
A multipart sender resumes framing and payload segments across transport credit windows: drain size considers the remaining suffix instead of whole segment length.
A multipart sender resumes framing and payload segments across transport credit windows: drain size considers the remaining suffix instead of whole segment length · case 03
A multipart sender resumes framing and payload segments across transport credit windows: drain size considers the remaining suffix instead of whole segment length.
A multipart sender resumes framing and payload segments across transport credit windows: drain size considers the remaining suffix instead of whole segment length · case 04
A multipart sender resumes framing and payload segments across transport credit windows: drain size considers the remaining suffix instead of whole segment length.
A multipart sender resumes framing and payload segments across transport credit windows: drain size considers the remaining suffix instead of whole segment length · case 05
A multipart sender resumes framing and payload segments across transport credit windows: drain size considers the remaining suffix instead of whole segment length.
A multipart sender resumes framing and payload segments across transport credit windows: a partially sent header resumes at its saved intra-header position · case 01
A multipart sender resumes framing and payload segments across transport credit windows: a partially sent header resumes at its saved intra-header position.
A multipart sender resumes framing and payload segments across transport credit windows: a partially sent header resumes at its saved intra-header position · case 02
A multipart sender resumes framing and payload segments across transport credit windows: a partially sent header resumes at its saved intra-header position.
A multipart sender resumes framing and payload segments across transport credit windows: a partially sent header resumes at its saved intra-header position · case 03
A multipart sender resumes framing and payload segments across transport credit windows: a partially sent header resumes at its saved intra-header position.
A multipart sender resumes framing and payload segments across transport credit windows: a partially sent header resumes at its saved intra-header position · case 04
A multipart sender resumes framing and payload segments across transport credit windows: a partially sent header resumes at its saved intra-header position.
A multipart sender resumes framing and payload segments across transport credit windows: a partially sent header resumes at its saved intra-header position · case 05
A multipart sender resumes framing and payload segments across transport credit windows: a partially sent header resumes at its saved intra-header position.
A multipart sender resumes framing and payload segments across transport credit windows: accepted bytes advance the cursor rather than replacing it · case 01
A multipart sender resumes framing and payload segments across transport credit windows: accepted bytes advance the cursor rather than replacing it.
A multipart sender resumes framing and payload segments across transport credit windows: accepted bytes advance the cursor rather than replacing it · case 02
A multipart sender resumes framing and payload segments across transport credit windows: accepted bytes advance the cursor rather than replacing it.
A multipart sender resumes framing and payload segments across transport credit windows: accepted bytes advance the cursor rather than replacing it · case 03
A multipart sender resumes framing and payload segments across transport credit windows: accepted bytes advance the cursor rather than replacing it.
A multipart sender resumes framing and payload segments across transport credit windows: accepted bytes advance the cursor rather than replacing it · case 04
A multipart sender resumes framing and payload segments across transport credit windows: accepted bytes advance the cursor rather than replacing it.
A multipart sender resumes framing and payload segments across transport credit windows: accepted bytes advance the cursor rather than replacing it · case 05
A multipart sender resumes framing and payload segments across transport credit windows: accepted bytes advance the cursor rather than replacing it.
A multipart sender resumes framing and payload segments across transport credit windows: transport credit is decremented by actual accepted bytes · case 01
A multipart sender resumes framing and payload segments across transport credit windows: transport credit is decremented by actual accepted bytes.
A multipart sender resumes framing and payload segments across transport credit windows: transport credit is decremented by actual accepted bytes · case 02
A multipart sender resumes framing and payload segments across transport credit windows: transport credit is decremented by actual accepted bytes.
A multipart sender resumes framing and payload segments across transport credit windows: transport credit is decremented by actual accepted bytes · case 03
A multipart sender resumes framing and payload segments across transport credit windows: transport credit is decremented by actual accepted bytes.
A multipart sender resumes framing and payload segments across transport credit windows: transport credit is decremented by actual accepted bytes · case 04
A multipart sender resumes framing and payload segments across transport credit windows: transport credit is decremented by actual accepted bytes.
A multipart sender resumes framing and payload segments across transport credit windows: transport credit is decremented by actual accepted bytes · case 05
A multipart sender resumes framing and payload segments across transport credit windows: transport credit is decremented by actual accepted bytes.
A multipart sender resumes framing and payload segments across transport credit windows: each transport window retains bytes emitted from all reached components · case 01
A multipart sender resumes framing and payload segments across transport credit windows: each transport window retains bytes emitted from all reached components.
A multipart sender resumes framing and payload segments across transport credit windows: each transport window retains bytes emitted from all reached components · case 02
A multipart sender resumes framing and payload segments across transport credit windows: each transport window retains bytes emitted from all reached components.
A multipart sender resumes framing and payload segments across transport credit windows: each transport window retains bytes emitted from all reached components · case 03
A multipart sender resumes framing and payload segments across transport credit windows: each transport window retains bytes emitted from all reached components.
A multipart sender resumes framing and payload segments across transport credit windows: each transport window retains bytes emitted from all reached components · case 04
A multipart sender resumes framing and payload segments across transport credit windows: each transport window retains bytes emitted from all reached components.
A multipart sender resumes framing and payload segments across transport credit windows: each transport window retains bytes emitted from all reached components · case 05
A multipart sender resumes framing and payload segments across transport credit windows: each transport window retains bytes emitted from all reached components.
A multipart sender resumes framing and payload segments across transport credit windows: zero-length framing components do not consume transport credit · case 01
A multipart sender resumes framing and payload segments across transport credit windows: zero-length framing components do not consume transport credit.
A multipart sender resumes framing and payload segments across transport credit windows: zero-length framing components do not consume transport credit · case 02
A multipart sender resumes framing and payload segments across transport credit windows: zero-length framing components do not consume transport credit.
A multipart sender resumes framing and payload segments across transport credit windows: zero-length framing components do not consume transport credit · case 03
A multipart sender resumes framing and payload segments across transport credit windows: zero-length framing components do not consume transport credit.
A multipart sender resumes framing and payload segments across transport credit windows: zero-length framing components do not consume transport credit · case 04
A multipart sender resumes framing and payload segments across transport credit windows: zero-length framing components do not consume transport credit.
A multipart sender resumes framing and payload segments across transport credit windows: zero-length framing components do not consume transport credit · case 05
A multipart sender resumes framing and payload segments across transport credit windows: zero-length framing components do not consume transport credit.
A multipart sender resumes framing and payload segments across transport credit windows: zero-byte windows remain visible to the transport caller · case 01
A multipart sender resumes framing and payload segments across transport credit windows: zero-byte windows remain visible to the transport caller.
A multipart sender resumes framing and payload segments across transport credit windows: zero-byte windows remain visible to the transport caller · case 02
A multipart sender resumes framing and payload segments across transport credit windows: zero-byte windows remain visible to the transport caller.
A multipart sender resumes framing and payload segments across transport credit windows: zero-byte windows remain visible to the transport caller · case 03
A multipart sender resumes framing and payload segments across transport credit windows: zero-byte windows remain visible to the transport caller.
A multipart sender resumes framing and payload segments across transport credit windows: zero-byte windows remain visible to the transport caller · case 04
A multipart sender resumes framing and payload segments across transport credit windows: zero-byte windows remain visible to the transport caller.
A multipart sender resumes framing and payload segments across transport credit windows: zero-byte windows remain visible to the transport caller · case 05
A multipart sender resumes framing and payload segments across transport credit windows: zero-byte windows remain visible to the transport caller.
Concurrent download clients share bounded origin range reads: canceled consumers do not schedule more origin byte reads · case 01
Concurrent download clients share bounded origin range reads: canceled consumers do not schedule more origin byte reads.
Concurrent download clients share bounded origin range reads: canceled consumers do not schedule more origin byte reads · case 02
Concurrent download clients share bounded origin range reads: canceled consumers do not schedule more origin byte reads.
Concurrent download clients share bounded origin range reads: canceled consumers do not schedule more origin byte reads · case 03
Concurrent download clients share bounded origin range reads: canceled consumers do not schedule more origin byte reads.
Concurrent download clients share bounded origin range reads: canceled consumers do not schedule more origin byte reads · case 04
Concurrent download clients share bounded origin range reads: canceled consumers do not schedule more origin byte reads.
Concurrent download clients share bounded origin range reads: canceled consumers do not schedule more origin byte reads · case 05
Concurrent download clients share bounded origin range reads: canceled consumers do not schedule more origin byte reads.
Concurrent download clients share bounded origin range reads: dispatch order follows consumer arrival rather than client names · case 01
Concurrent download clients share bounded origin range reads: dispatch order follows consumer arrival rather than client names.
Concurrent download clients share bounded origin range reads: dispatch order follows consumer arrival rather than client names · case 02
Concurrent download clients share bounded origin range reads: dispatch order follows consumer arrival rather than client names.
Concurrent download clients share bounded origin range reads: dispatch order follows consumer arrival rather than client names · case 03
Concurrent download clients share bounded origin range reads: dispatch order follows consumer arrival rather than client names.
Concurrent download clients share bounded origin range reads: dispatch order follows consumer arrival rather than client names · case 04
Concurrent download clients share bounded origin range reads: dispatch order follows consumer arrival rather than client names.
Concurrent download clients share bounded origin range reads: dispatch order follows consumer arrival rather than client names · case 05
Concurrent download clients share bounded origin range reads: dispatch order follows consumer arrival rather than client names.
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 ↗