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 range client removes transfer framing before applying representation offsets: body data starts after both bytes of size-line CRLF · case 01
A range client removes transfer framing before applying representation offsets: body data starts after both bytes of size-line CRLF.
A range client removes transfer framing before applying representation offsets: body data starts after both bytes of size-line CRLF · case 02
A range client removes transfer framing before applying representation offsets: body data starts after both bytes of size-line CRLF.
A range client removes transfer framing before applying representation offsets: body data starts after both bytes of size-line CRLF · case 03
A range client removes transfer framing before applying representation offsets: body data starts after both bytes of size-line CRLF.
A range client removes transfer framing before applying representation offsets: body data starts after both bytes of size-line CRLF · case 04
A range client removes transfer framing before applying representation offsets: body data starts after both bytes of size-line CRLF.
A range client removes transfer framing before applying representation offsets: body data starts after both bytes of size-line CRLF · case 05
A range client removes transfer framing before applying representation offsets: body data starts after both bytes of size-line CRLF.
A range client removes transfer framing before applying representation offsets: the zero chunk starts trailer parsing without entering body accumulation · case 01
A range client removes transfer framing before applying representation offsets: the zero chunk starts trailer parsing without entering body accumulation.
A range client removes transfer framing before applying representation offsets: the zero chunk starts trailer parsing without entering body accumulation · case 02
A range client removes transfer framing before applying representation offsets: the zero chunk starts trailer parsing without entering body accumulation.
A range client removes transfer framing before applying representation offsets: the zero chunk starts trailer parsing without entering body accumulation · case 03
A range client removes transfer framing before applying representation offsets: the zero chunk starts trailer parsing without entering body accumulation.
A range client removes transfer framing before applying representation offsets: the zero chunk starts trailer parsing without entering body accumulation · case 04
A range client removes transfer framing before applying representation offsets: the zero chunk starts trailer parsing without entering body accumulation.
A range client removes transfer framing before applying representation offsets: the zero chunk starts trailer parsing without entering body accumulation · case 05
A range client removes transfer framing before applying representation offsets: the zero chunk starts trailer parsing without entering body accumulation.
A range client removes transfer framing before applying representation offsets: chunk payload lengths do not excuse invalid framing separators · case 01
A range client removes transfer framing before applying representation offsets: chunk payload lengths do not excuse invalid framing separators.
A range client removes transfer framing before applying representation offsets: chunk payload lengths do not excuse invalid framing separators · case 02
A range client removes transfer framing before applying representation offsets: chunk payload lengths do not excuse invalid framing separators.
A range client removes transfer framing before applying representation offsets: chunk payload lengths do not excuse invalid framing separators · case 03
A range client removes transfer framing before applying representation offsets: chunk payload lengths do not excuse invalid framing separators.
A range client removes transfer framing before applying representation offsets: chunk payload lengths do not excuse invalid framing separators · case 04
A range client removes transfer framing before applying representation offsets: chunk payload lengths do not excuse invalid framing separators.
A range client removes transfer framing before applying representation offsets: chunk payload lengths do not excuse invalid framing separators · case 05
A range client removes transfer framing before applying representation offsets: chunk payload lengths do not excuse invalid framing separators.
A range client removes transfer framing before applying representation offsets: each next size line begins after the payload framing CRLF · case 01
A range client removes transfer framing before applying representation offsets: each next size line begins after the payload framing CRLF.
A range client removes transfer framing before applying representation offsets: each next size line begins after the payload framing CRLF · case 02
A range client removes transfer framing before applying representation offsets: each next size line begins after the payload framing CRLF.
A range client removes transfer framing before applying representation offsets: each next size line begins after the payload framing CRLF · case 03
A range client removes transfer framing before applying representation offsets: each next size line begins after the payload framing CRLF.
A range client removes transfer framing before applying representation offsets: each next size line begins after the payload framing CRLF · case 04
A range client removes transfer framing before applying representation offsets: each next size line begins after the payload framing CRLF.
A range client removes transfer framing before applying representation offsets: each next size line begins after the payload framing CRLF · case 05
A range client removes transfer framing before applying representation offsets: each next size line begins after the payload framing CRLF.
A range client removes transfer framing before applying representation offsets: range offsets address decoded payload rather than transfer framing · case 01
A range client removes transfer framing before applying representation offsets: range offsets address decoded payload rather than transfer framing.
A range client removes transfer framing before applying representation offsets: range offsets address decoded payload rather than transfer framing · case 02
A range client removes transfer framing before applying representation offsets: range offsets address decoded payload rather than transfer framing.
A range client removes transfer framing before applying representation offsets: range offsets address decoded payload rather than transfer framing · case 03
A range client removes transfer framing before applying representation offsets: range offsets address decoded payload rather than transfer framing.
A range client removes transfer framing before applying representation offsets: range offsets address decoded payload rather than transfer framing · case 04
A range client removes transfer framing before applying representation offsets: range offsets address decoded payload rather than transfer framing.
A range client removes transfer framing before applying representation offsets: range offsets address decoded payload rather than transfer framing · case 05
A range client removes transfer framing before applying representation offsets: range offsets address decoded payload rather than transfer framing.
A range client removes transfer framing before applying representation offsets: the decoded byte cap is enforced across all chunks · case 01
A range client removes transfer framing before applying representation offsets: the decoded byte cap is enforced across all chunks.
A range client removes transfer framing before applying representation offsets: the decoded byte cap is enforced across all chunks · case 02
A range client removes transfer framing before applying representation offsets: the decoded byte cap is enforced across all chunks.
A range client removes transfer framing before applying representation offsets: the decoded byte cap is enforced across all chunks · case 03
A range client removes transfer framing before applying representation offsets: the decoded byte cap is enforced across all chunks.
A range client removes transfer framing before applying representation offsets: the decoded byte cap is enforced across all chunks · case 04
A range client removes transfer framing before applying representation offsets: the decoded byte cap is enforced across all chunks.
A range client removes transfer framing before applying representation offsets: the decoded byte cap is enforced across all chunks · case 05
A range client removes transfer framing before applying representation offsets: the decoded byte cap is enforced across all chunks.
A range client removes transfer framing before applying representation offsets: bytes after the trailer terminator cannot extend this response · case 01
A range client removes transfer framing before applying representation offsets: bytes after the trailer terminator cannot extend this response.
A range client removes transfer framing before applying representation offsets: bytes after the trailer terminator cannot extend this response · case 02
A range client removes transfer framing before applying representation offsets: bytes after the trailer terminator cannot extend this response.
A range client removes transfer framing before applying representation offsets: bytes after the trailer terminator cannot extend this response · case 03
A range client removes transfer framing before applying representation offsets: bytes after the trailer terminator cannot extend this response.
A range client removes transfer framing before applying representation offsets: bytes after the trailer terminator cannot extend this response · case 04
A range client removes transfer framing before applying representation offsets: bytes after the trailer terminator cannot extend this response.
A range client removes transfer framing before applying representation offsets: bytes after the trailer terminator cannot extend this response · case 05
A range client removes transfer framing before applying representation offsets: bytes after the trailer terminator cannot extend this response.
A range client removes transfer framing before applying representation offsets: all parsed trailer fields retain their wire order · case 01
A range client removes transfer framing before applying representation offsets: all parsed trailer fields retain their wire order.
A range client removes transfer framing before applying representation offsets: all parsed trailer fields retain their wire order · case 02
A range client removes transfer framing before applying representation offsets: all parsed trailer fields retain their wire order.
A range client removes transfer framing before applying representation offsets: all parsed trailer fields retain their wire order · case 03
A range client removes transfer framing before applying representation offsets: all parsed trailer fields retain their wire order.
A range client removes transfer framing before applying representation offsets: all parsed trailer fields retain their wire order · case 04
A range client removes transfer framing before applying representation offsets: all parsed trailer fields retain their wire order.
A range client removes transfer framing before applying representation offsets: all parsed trailer fields retain their wire order · case 05
A range client removes transfer framing before applying representation offsets: all parsed trailer fields retain their wire order.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: both magic bytes distinguish range records from unrelated cache files · case 01
A persisted partial-response cache record keeps byte coverage and revision metadata intact: both magic bytes distinguish range records from unrelated cache files.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: both magic bytes distinguish range records from unrelated cache files · case 02
A persisted partial-response cache record keeps byte coverage and revision metadata intact: both magic bytes distinguish range records from unrelated cache files.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: both magic bytes distinguish range records from unrelated cache files · case 03
A persisted partial-response cache record keeps byte coverage and revision metadata intact: both magic bytes distinguish range records from unrelated cache files.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: both magic bytes distinguish range records from unrelated cache files · case 04
A persisted partial-response cache record keeps byte coverage and revision metadata intact: both magic bytes distinguish range records from unrelated cache files.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: both magic bytes distinguish range records from unrelated cache files · case 05
A persisted partial-response cache record keeps byte coverage and revision metadata intact: both magic bytes distinguish range records from unrelated cache files.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unsupported record versions do not reuse the current fragment layout · case 01
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unsupported record versions do not reuse the current fragment layout.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unsupported record versions do not reuse the current fragment layout · case 02
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unsupported record versions do not reuse the current fragment layout.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unsupported record versions do not reuse the current fragment layout · case 03
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unsupported record versions do not reuse the current fragment layout.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unsupported record versions do not reuse the current fragment layout · case 04
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unsupported record versions do not reuse the current fragment layout.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unsupported record versions do not reuse the current fragment layout · case 05
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unsupported record versions do not reuse the current fragment layout.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unknown envelope flags cannot silently change fragment meaning · case 01
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unknown envelope flags cannot silently change fragment meaning.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unknown envelope flags cannot silently change fragment meaning · case 02
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unknown envelope flags cannot silently change fragment meaning.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unknown envelope flags cannot silently change fragment meaning · case 03
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unknown envelope flags cannot silently change fragment meaning.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unknown envelope flags cannot silently change fragment meaning · case 04
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unknown envelope flags cannot silently change fragment meaning.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unknown envelope flags cannot silently change fragment meaning · case 05
A persisted partial-response cache record keeps byte coverage and revision metadata intact: unknown envelope flags cannot silently change fragment meaning.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: coverage metadata is verified along with cached payload bytes · case 01
A persisted partial-response cache record keeps byte coverage and revision metadata intact: coverage metadata is verified along with cached payload bytes.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: coverage metadata is verified along with cached payload bytes · case 02
A persisted partial-response cache record keeps byte coverage and revision metadata intact: coverage metadata is verified along with cached payload bytes.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: coverage metadata is verified along with cached payload bytes · case 03
A persisted partial-response cache record keeps byte coverage and revision metadata intact: coverage metadata is verified along with cached payload bytes.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: coverage metadata is verified along with cached payload bytes · case 04
A persisted partial-response cache record keeps byte coverage and revision metadata intact: coverage metadata is verified along with cached payload bytes.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: coverage metadata is verified along with cached payload bytes · case 05
A persisted partial-response cache record keeps byte coverage and revision metadata intact: coverage metadata is verified along with cached payload bytes.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persisted generations retain their high byte · case 01
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persisted generations retain their high byte.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persisted generations retain their high byte · case 02
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persisted generations retain their high byte.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persisted generations retain their high byte · case 03
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persisted generations retain their high byte.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persisted generations retain their high byte · case 04
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persisted generations retain their high byte.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persisted generations retain their high byte · case 05
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persisted generations retain their high byte.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: the complete representation length is decoded independently of fragment size · case 01
A persisted partial-response cache record keeps byte coverage and revision metadata intact: the complete representation length is decoded independently of fragment size.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: the complete representation length is decoded independently of fragment size · case 02
A persisted partial-response cache record keeps byte coverage and revision metadata intact: the complete representation length is decoded independently of fragment size.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: the complete representation length is decoded independently of fragment size · case 03
A persisted partial-response cache record keeps byte coverage and revision metadata intact: the complete representation length is decoded independently of fragment size.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: the complete representation length is decoded independently of fragment size · case 04
A persisted partial-response cache record keeps byte coverage and revision metadata intact: the complete representation length is decoded independently of fragment size.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: the complete representation length is decoded independently of fragment size · case 05
A persisted partial-response cache record keeps byte coverage and revision metadata intact: the complete representation length is decoded independently of fragment size.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: fragments beyond the first256 bytes retain absolute placement · case 01
A persisted partial-response cache record keeps byte coverage and revision metadata intact: fragments beyond the first256 bytes retain absolute placement.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: fragments beyond the first256 bytes retain absolute placement · case 02
A persisted partial-response cache record keeps byte coverage and revision metadata intact: fragments beyond the first256 bytes retain absolute placement.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: fragments beyond the first256 bytes retain absolute placement · case 03
A persisted partial-response cache record keeps byte coverage and revision metadata intact: fragments beyond the first256 bytes retain absolute placement.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: fragments beyond the first256 bytes retain absolute placement · case 04
A persisted partial-response cache record keeps byte coverage and revision metadata intact: fragments beyond the first256 bytes retain absolute placement.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: fragments beyond the first256 bytes retain absolute placement · case 05
A persisted partial-response cache record keeps byte coverage and revision metadata intact: fragments beyond the first256 bytes retain absolute placement.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: stored fragment data cannot extend past the recorded representation · case 01
A persisted partial-response cache record keeps byte coverage and revision metadata intact: stored fragment data cannot extend past the recorded representation.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: stored fragment data cannot extend past the recorded representation · case 02
A persisted partial-response cache record keeps byte coverage and revision metadata intact: stored fragment data cannot extend past the recorded representation.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: stored fragment data cannot extend past the recorded representation · case 03
A persisted partial-response cache record keeps byte coverage and revision metadata intact: stored fragment data cannot extend past the recorded representation.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: stored fragment data cannot extend past the recorded representation · case 04
A persisted partial-response cache record keeps byte coverage and revision metadata intact: stored fragment data cannot extend past the recorded representation.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: stored fragment data cannot extend past the recorded representation · case 05
A persisted partial-response cache record keeps byte coverage and revision metadata intact: stored fragment data cannot extend past the recorded representation.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persistent records cannot assign the same byte to two fragments · case 01
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persistent records cannot assign the same byte to two fragments.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persistent records cannot assign the same byte to two fragments · case 02
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persistent records cannot assign the same byte to two fragments.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persistent records cannot assign the same byte to two fragments · case 03
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persistent records cannot assign the same byte to two fragments.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persistent records cannot assign the same byte to two fragments · case 04
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persistent records cannot assign the same byte to two fragments.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persistent records cannot assign the same byte to two fragments · case 05
A persisted partial-response cache record keeps byte coverage and revision metadata intact: persistent records cannot assign the same byte to two fragments.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: envelope fragment count must consume the entire record payload · case 01
A persisted partial-response cache record keeps byte coverage and revision metadata intact: envelope fragment count must consume the entire record payload.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: envelope fragment count must consume the entire record payload · case 02
A persisted partial-response cache record keeps byte coverage and revision metadata intact: envelope fragment count must consume the entire record payload.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: envelope fragment count must consume the entire record payload · case 03
A persisted partial-response cache record keeps byte coverage and revision metadata intact: envelope fragment count must consume the entire record payload.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: envelope fragment count must consume the entire record payload · case 04
A persisted partial-response cache record keeps byte coverage and revision metadata intact: envelope fragment count must consume the entire record payload.
A persisted partial-response cache record keeps byte coverage and revision metadata intact: envelope fragment count must consume the entire record payload · case 05
A persisted partial-response cache record keeps byte coverage and revision metadata intact: envelope fragment count must consume the entire record payload.
An upload status endpoint reports committed byte coverage: arrival order cannot split or reverse acknowledged byte runs · case 01
An upload status endpoint reports committed byte coverage: arrival order cannot split or reverse acknowledged byte runs.
An upload status endpoint reports committed byte coverage: arrival order cannot split or reverse acknowledged byte runs · case 02
An upload status endpoint reports committed byte coverage: arrival order cannot split or reverse acknowledged byte runs.
An upload status endpoint reports committed byte coverage: arrival order cannot split or reverse acknowledged byte runs · case 03
An upload status endpoint reports committed byte coverage: arrival order cannot split or reverse acknowledged byte runs.
An upload status endpoint reports committed byte coverage: arrival order cannot split or reverse acknowledged byte runs · case 04
An upload status endpoint reports committed byte coverage: arrival order cannot split or reverse acknowledged byte runs.
An upload status endpoint reports committed byte coverage: arrival order cannot split or reverse acknowledged byte runs · case 05
An upload status endpoint reports committed byte coverage: arrival order cannot split or reverse acknowledged byte runs.
An upload status endpoint reports committed byte coverage: repeated committed byte reports count only once · case 01
An upload status endpoint reports committed byte coverage: repeated committed byte reports count only once.
An upload status endpoint reports committed byte coverage: repeated committed byte reports count only once · case 02
An upload status endpoint reports committed byte coverage: repeated committed byte reports count only once.
An upload status endpoint reports committed byte coverage: repeated committed byte reports count only once · case 03
An upload status endpoint reports committed byte coverage: repeated committed byte reports count only once.
An upload status endpoint reports committed byte coverage: repeated committed byte reports count only once · case 04
An upload status endpoint reports committed byte coverage: repeated committed byte reports count only once.
An upload status endpoint reports committed byte coverage: repeated committed byte reports count only once · case 05
An upload status endpoint reports committed byte coverage: repeated committed byte reports count only once.
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 ↗