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
Report redirect failures with the failing phase and completed request context: attempted target context · case 01
Report redirect failures with the failing phase and completed request context: the attempted target context branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: attempted target context · case 02
Report redirect failures with the failing phase and completed request context: the attempted target context branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: attempted target context · case 03
Report redirect failures with the failing phase and completed request context: the attempted target context branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: attempted target context · case 04
Report redirect failures with the failing phase and completed request context: the attempted target context branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: attempted target context · case 05
Report redirect failures with the failing phase and completed request context: the attempted target context branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: rejected target not completed · case 01
Report redirect failures with the failing phase and completed request context: the rejected target not completed branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: rejected target not completed · case 02
Report redirect failures with the failing phase and completed request context: the rejected target not completed branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: rejected target not completed · case 03
Report redirect failures with the failing phase and completed request context: the rejected target not completed branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: rejected target not completed · case 04
Report redirect failures with the failing phase and completed request context: the rejected target not completed branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: rejected target not completed · case 05
Report redirect failures with the failing phase and completed request context: the rejected target not completed branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: error code optional · case 01
Report redirect failures with the failing phase and completed request context: the error code optional branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: error code optional · case 02
Report redirect failures with the failing phase and completed request context: the error code optional branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: error code optional · case 03
Report redirect failures with the failing phase and completed request context: the error code optional branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: error code optional · case 04
Report redirect failures with the failing phase and completed request context: the error code optional branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: error code optional · case 05
Report redirect failures with the failing phase and completed request context: the error code optional branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: failure from code · case 01
Report redirect failures with the failing phase and completed request context: the failure from code branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: failure from code · case 02
Report redirect failures with the failing phase and completed request context: the failure from code branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: failure from code · case 03
Report redirect failures with the failing phase and completed request context: the failure from code branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: failure from code · case 04
Report redirect failures with the failing phase and completed request context: the failure from code branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: failure from code · case 05
Report redirect failures with the failing phase and completed request context: the failure from code branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: last completed safe empty · case 01
Report redirect failures with the failing phase and completed request context: the last completed safe empty branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: last completed safe empty · case 02
Report redirect failures with the failing phase and completed request context: the last completed safe empty branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: last completed safe empty · case 03
Report redirect failures with the failing phase and completed request context: the last completed safe empty branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: last completed safe empty · case 04
Report redirect failures with the failing phase and completed request context: the last completed safe empty branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: last completed safe empty · case 05
Report redirect failures with the failing phase and completed request context: the last completed safe empty branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: pre dispatch failure · case 01
Report redirect failures with the failing phase and completed request context: the pre dispatch failure branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: pre dispatch failure · case 02
Report redirect failures with the failing phase and completed request context: the pre dispatch failure branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: pre dispatch failure · case 03
Report redirect failures with the failing phase and completed request context: the pre dispatch failure branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: pre dispatch failure · case 04
Report redirect failures with the failing phase and completed request context: the pre dispatch failure branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: pre dispatch failure · case 05
Report redirect failures with the failing phase and completed request context: the pre dispatch failure branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: completed hop path order · case 01
Report redirect failures with the failing phase and completed request context: the completed hop path order branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: completed hop path order · case 02
Report redirect failures with the failing phase and completed request context: the completed hop path order branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: completed hop path order · case 03
Report redirect failures with the failing phase and completed request context: the completed hop path order branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: completed hop path order · case 04
Report redirect failures with the failing phase and completed request context: the completed hop path order branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: completed hop path order · case 05
Report redirect failures with the failing phase and completed request context: the completed hop path order branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: unsent target flag · case 01
Report redirect failures with the failing phase and completed request context: the unsent target flag branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: unsent target flag · case 02
Report redirect failures with the failing phase and completed request context: the unsent target flag branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: unsent target flag · case 03
Report redirect failures with the failing phase and completed request context: the unsent target flag branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: unsent target flag · case 04
Report redirect failures with the failing phase and completed request context: the unsent target flag branch emits an incorrect decision.
Report redirect failures with the failing phase and completed request context: unsent target flag · case 05
Report redirect failures with the failing phase and completed request context: the unsent target flag branch emits an incorrect decision.
Replay source snapshot: Body mutation after the first attempt changes replay bytes · case 01
Body mutation after the first attempt changes replay bytes
Replay source snapshot: Body mutation after the first attempt changes replay bytes · case 02
Body mutation after the first attempt changes replay bytes
Replay source snapshot: Body mutation after the first attempt changes replay bytes · case 03
Body mutation after the first attempt changes replay bytes
Replay source snapshot: Body mutation after the first attempt changes replay bytes · case 04
Body mutation after the first attempt changes replay bytes
Replay source snapshot: Body mutation after the first attempt changes replay bytes · case 05
Body mutation after the first attempt changes replay bytes
Replay source snapshot: Retry rewinds into a prefix preceding the request body · case 01
Retry rewinds into a prefix preceding the request body
Replay source snapshot: Retry rewinds into a prefix preceding the request body · case 02
Retry rewinds into a prefix preceding the request body
Replay source snapshot: Retry rewinds into a prefix preceding the request body · case 03
Retry rewinds into a prefix preceding the request body
Replay source snapshot: Retry rewinds into a prefix preceding the request body · case 04
Retry rewinds into a prefix preceding the request body
Replay source snapshot: Retry rewinds into a prefix preceding the request body · case 05
Retry rewinds into a prefix preceding the request body
Replay source snapshot: Initial upload ignores the captured stream origin · case 01
Initial upload ignores the captured stream origin
Replay source snapshot: Initial upload ignores the captured stream origin · case 02
Initial upload ignores the captured stream origin
Replay source snapshot: Initial upload ignores the captured stream origin · case 03
Initial upload ignores the captured stream origin
Replay source snapshot: Initial upload ignores the captured stream origin · case 04
Initial upload ignores the captured stream origin
Replay source snapshot: Initial upload ignores the captured stream origin · case 05
Initial upload ignores the captured stream origin
Replay source snapshot: Opening a new empty body retains the previous closed state · case 01
Opening a new empty body retains the previous closed state
Replay source snapshot: Opening a new empty body retains the previous closed state · case 02
Opening a new empty body retains the previous closed state
Replay source snapshot: Opening a new empty body retains the previous closed state · case 03
Opening a new empty body retains the previous closed state
Replay source snapshot: Opening a new empty body retains the previous closed state · case 04
Opening a new empty body retains the previous closed state
Replay source snapshot: Opening a new empty body retains the previous closed state · case 05
Opening a new empty body retains the previous closed state
Replay source snapshot: Subsequent upload reads resend a prefix or exceed requested size · case 01
Subsequent upload reads resend a prefix or exceed requested size
Replay source snapshot: Subsequent upload reads resend a prefix or exceed requested size · case 02
Subsequent upload reads resend a prefix or exceed requested size
Replay source snapshot: Subsequent upload reads resend a prefix or exceed requested size · case 03
Subsequent upload reads resend a prefix or exceed requested size
Replay source snapshot: Subsequent upload reads resend a prefix or exceed requested size · case 04
Subsequent upload reads resend a prefix or exceed requested size
Replay source snapshot: Subsequent upload reads resend a prefix or exceed requested size · case 05
Subsequent upload reads resend a prefix or exceed requested size
Replay source snapshot: Upload cursor counts reads rather than bytes already consumed · case 01
Upload cursor counts reads rather than bytes already consumed
Replay source snapshot: Upload cursor counts reads rather than bytes already consumed · case 02
Upload cursor counts reads rather than bytes already consumed
Replay source snapshot: Upload cursor counts reads rather than bytes already consumed · case 03
Upload cursor counts reads rather than bytes already consumed
Replay source snapshot: Upload cursor counts reads rather than bytes already consumed · case 04
Upload cursor counts reads rather than bytes already consumed
Replay source snapshot: Upload cursor counts reads rather than bytes already consumed · case 05
Upload cursor counts reads rather than bytes already consumed
Replay source snapshot: A partially consumed body remains readable after cancellation closes it · case 01
A partially consumed body remains readable after cancellation closes it
Replay source snapshot: A partially consumed body remains readable after cancellation closes it · case 02
A partially consumed body remains readable after cancellation closes it
Replay source snapshot: A partially consumed body remains readable after cancellation closes it · case 03
A partially consumed body remains readable after cancellation closes it
Replay source snapshot: A partially consumed body remains readable after cancellation closes it · case 04
A partially consumed body remains readable after cancellation closes it
Replay source snapshot: A partially consumed body remains readable after cancellation closes it · case 05
A partially consumed body remains readable after cancellation closes it
Replay source snapshot: Closed upload reads are mistaken for successful EOF · case 01
Closed upload reads are mistaken for successful EOF
Replay source snapshot: Closed upload reads are mistaken for successful EOF · case 02
Closed upload reads are mistaken for successful EOF
Replay source snapshot: Closed upload reads are mistaken for successful EOF · case 03
Closed upload reads are mistaken for successful EOF
Replay source snapshot: Closed upload reads are mistaken for successful EOF · case 04
Closed upload reads are mistaken for successful EOF
Replay source snapshot: Closed upload reads are mistaken for successful EOF · case 05
Closed upload reads are mistaken for successful EOF
Replay source snapshot: Retry preserves an already consumed cursor · case 01
Retry preserves an already consumed cursor
Replay source snapshot: Retry preserves an already consumed cursor · case 02
Retry preserves an already consumed cursor
Replay source snapshot: Retry preserves an already consumed cursor · case 03
Retry preserves an already consumed cursor
Replay source snapshot: Retry preserves an already consumed cursor · case 04
Retry preserves an already consumed cursor
Replay source snapshot: Retry preserves an already consumed cursor · case 05
Retry preserves an already consumed cursor
Replay source snapshot: A retry reports rewind success for a released body · case 01
A retry reports rewind success for a released body
Replay source snapshot: A retry reports rewind success for a released body · case 02
A retry reports rewind success for a released body
Replay source snapshot: A retry reports rewind success for a released body · case 03
A retry reports rewind success for a released body
Replay source snapshot: A retry reports rewind success for a released body · case 04
A retry reports rewind success for a released body
Replay source snapshot: A retry reports rewind success for a released body · case 05
A retry reports rewind success for a released body
One-shot request body replay refusal: A fresh one-shot body inherits consumption from the previous request · case 01
A fresh one-shot body inherits consumption from the previous request
One-shot request body replay refusal: A fresh one-shot body inherits consumption from the previous request · case 02
A fresh one-shot body inherits consumption from the previous request
One-shot request body replay refusal: A fresh one-shot body inherits consumption from the previous request · case 03
A fresh one-shot body inherits consumption from the previous request
One-shot request body replay refusal: A fresh one-shot body inherits consumption from the previous request · case 04
A fresh one-shot body inherits consumption from the previous request
One-shot request body replay refusal: A fresh one-shot body inherits consumption from the previous request · case 05
A fresh one-shot body inherits consumption from the previous request
One-shot request body replay refusal: A later zero-byte send hides earlier consumption · case 01
A later zero-byte send hides earlier consumption
One-shot request body replay refusal: A later zero-byte send hides earlier consumption · case 02
A later zero-byte send hides earlier consumption
One-shot request body replay refusal: A later zero-byte send hides earlier consumption · case 03
A later zero-byte send hides earlier consumption
One-shot request body replay refusal: A later zero-byte send hides earlier consumption · case 04
A later zero-byte send hides earlier consumption
One-shot request body replay refusal: A later zero-byte send hides earlier consumption · case 05
A later zero-byte send hides earlier consumption
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 ↗