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
Teardown returned after cancellation is never disposed · case 01
Teardown returned after cancellation is never disposed; the returned lifecycle plan violates the stated transition contract.
Teardown returned after cancellation is never disposed · case 02
Teardown returned after cancellation is never disposed; the returned lifecycle plan violates the stated transition contract.
Teardown returned after cancellation is never disposed · case 03
Teardown returned after cancellation is never disposed; the returned lifecycle plan violates the stated transition contract.
Teardown returned after cancellation is never disposed · case 04
Teardown returned after cancellation is never disposed; the returned lifecycle plan violates the stated transition contract.
Teardown returned after cancellation is never disposed · case 05
Teardown returned after cancellation is never disposed; the returned lifecycle plan violates the stated transition contract.
A falsey subscription handle is mistaken for no handle · case 01
A falsey subscription handle is mistaken for no handle; the returned lifecycle plan violates the stated transition contract.
A falsey subscription handle is mistaken for no handle · case 02
A falsey subscription handle is mistaken for no handle; the returned lifecycle plan violates the stated transition contract.
A falsey subscription handle is mistaken for no handle · case 03
A falsey subscription handle is mistaken for no handle; the returned lifecycle plan violates the stated transition contract.
A falsey subscription handle is mistaken for no handle · case 04
A falsey subscription handle is mistaken for no handle; the returned lifecycle plan violates the stated transition contract.
A falsey subscription handle is mistaken for no handle · case 05
A falsey subscription handle is mistaken for no handle; the returned lifecycle plan violates the stated transition contract.
A subscribe exception after synchronous completion reopens the error channel · case 01
A subscribe exception after synchronous completion reopens the error channel; the returned lifecycle plan violates the stated transition contract.
A subscribe exception after synchronous completion reopens the error channel · case 02
A subscribe exception after synchronous completion reopens the error channel; the returned lifecycle plan violates the stated transition contract.
A subscribe exception after synchronous completion reopens the error channel · case 03
A subscribe exception after synchronous completion reopens the error channel; the returned lifecycle plan violates the stated transition contract.
A subscribe exception after synchronous completion reopens the error channel · case 04
A subscribe exception after synchronous completion reopens the error channel; the returned lifecycle plan violates the stated transition contract.
A subscribe exception after synchronous completion reopens the error channel · case 05
A subscribe exception after synchronous completion reopens the error channel; the returned lifecycle plan violates the stated transition contract.
The source initialization catch boundary claims callback-origin exceptions · case 01
The source initialization catch boundary claims callback-origin exceptions; the returned lifecycle plan violates the stated transition contract.
The source initialization catch boundary claims callback-origin exceptions · case 02
The source initialization catch boundary claims callback-origin exceptions; the returned lifecycle plan violates the stated transition contract.
The source initialization catch boundary claims callback-origin exceptions · case 03
The source initialization catch boundary claims callback-origin exceptions; the returned lifecycle plan violates the stated transition contract.
The source initialization catch boundary claims callback-origin exceptions · case 04
The source initialization catch boundary claims callback-origin exceptions; the returned lifecycle plan violates the stated transition contract.
The source initialization catch boundary claims callback-origin exceptions · case 05
The source initialization catch boundary claims callback-origin exceptions; the returned lifecycle plan violates the stated transition contract.
A subscription is considered ready before handle installation · case 01
A subscription is considered ready before handle installation; the returned lifecycle plan violates the stated transition contract.
A subscription is considered ready before handle installation · case 02
A subscription is considered ready before handle installation; the returned lifecycle plan violates the stated transition contract.
A subscription is considered ready before handle installation · case 03
A subscription is considered ready before handle installation; the returned lifecycle plan violates the stated transition contract.
A subscription is considered ready before handle installation · case 04
A subscription is considered ready before handle installation; the returned lifecycle plan violates the stated transition contract.
A subscription is considered ready before handle installation · case 05
A subscription is considered ready before handle installation; the returned lifecycle plan violates the stated transition contract.
Subscription initialization drops later groups of returned disposers · case 01
Subscription initialization drops later groups of returned disposers; the returned lifecycle plan violates the stated transition contract.
Subscription initialization drops later groups of returned disposers · case 02
Subscription initialization drops later groups of returned disposers; the returned lifecycle plan violates the stated transition contract.
Subscription initialization drops later groups of returned disposers · case 03
Subscription initialization drops later groups of returned disposers; the returned lifecycle plan violates the stated transition contract.
Subscription initialization drops later groups of returned disposers · case 04
Subscription initialization drops later groups of returned disposers; the returned lifecycle plan violates the stated transition contract.
Subscription initialization drops later groups of returned disposers · case 05
Subscription initialization drops later groups of returned disposers; the returned lifecycle plan violates the stated transition contract.
Startup token reuse creates duplicate pending subscription handshakes · case 01
Startup token reuse creates duplicate pending subscription handshakes; the returned lifecycle plan violates the stated transition contract.
Startup token reuse creates duplicate pending subscription handshakes · case 02
Startup token reuse creates duplicate pending subscription handshakes; the returned lifecycle plan violates the stated transition contract.
Startup token reuse creates duplicate pending subscription handshakes · case 03
Startup token reuse creates duplicate pending subscription handshakes; the returned lifecycle plan violates the stated transition contract.
Startup token reuse creates duplicate pending subscription handshakes · case 04
Startup token reuse creates duplicate pending subscription handshakes; the returned lifecycle plan violates the stated transition contract.
Startup token reuse creates duplicate pending subscription handshakes · case 05
Startup token reuse creates duplicate pending subscription handshakes; the returned lifecycle plan violates the stated transition contract.
Subscription handshake replaces a valid zero handle with a sentinel · case 01
Subscription handshake replaces a valid zero handle with a sentinel; the returned lifecycle plan violates the stated transition contract.
Subscription handshake replaces a valid zero handle with a sentinel · case 02
Subscription handshake replaces a valid zero handle with a sentinel; the returned lifecycle plan violates the stated transition contract.
Subscription handshake replaces a valid zero handle with a sentinel · case 03
Subscription handshake replaces a valid zero handle with a sentinel; the returned lifecycle plan violates the stated transition contract.
Subscription handshake replaces a valid zero handle with a sentinel · case 04
Subscription handshake replaces a valid zero handle with a sentinel; the returned lifecycle plan violates the stated transition contract.
Subscription handshake replaces a valid zero handle with a sentinel · case 05
Subscription handshake replaces a valid zero handle with a sentinel; the returned lifecycle plan violates the stated transition contract.
Composite teardown runs resources in forward acquisition order · case 01
Composite teardown runs resources in forward acquisition order; the returned lifecycle plan violates the stated transition contract.
Composite teardown runs resources in forward acquisition order · case 02
Composite teardown runs resources in forward acquisition order; the returned lifecycle plan violates the stated transition contract.
Composite teardown runs resources in forward acquisition order · case 03
Composite teardown runs resources in forward acquisition order; the returned lifecycle plan violates the stated transition contract.
Composite teardown runs resources in forward acquisition order · case 04
Composite teardown runs resources in forward acquisition order; the returned lifecycle plan violates the stated transition contract.
Composite teardown runs resources in forward acquisition order · case 05
Composite teardown runs resources in forward acquisition order; the returned lifecycle plan violates the stated transition contract.
Adding teardown to a closed subscription silently drops cleanup · case 01
Adding teardown to a closed subscription silently drops cleanup; the returned lifecycle plan violates the stated transition contract.
Adding teardown to a closed subscription silently drops cleanup · case 02
Adding teardown to a closed subscription silently drops cleanup; the returned lifecycle plan violates the stated transition contract.
Adding teardown to a closed subscription silently drops cleanup · case 03
Adding teardown to a closed subscription silently drops cleanup; the returned lifecycle plan violates the stated transition contract.
Adding teardown to a closed subscription silently drops cleanup · case 04
Adding teardown to a closed subscription silently drops cleanup; the returned lifecycle plan violates the stated transition contract.
Adding teardown to a closed subscription silently drops cleanup · case 05
Adding teardown to a closed subscription silently drops cleanup; the returned lifecycle plan violates the stated transition contract.
A closed composite stores a new disposer for an unreachable future close · case 01
A closed composite stores a new disposer for an unreachable future close; the returned lifecycle plan violates the stated transition contract.
A closed composite stores a new disposer for an unreachable future close · case 02
A closed composite stores a new disposer for an unreachable future close; the returned lifecycle plan violates the stated transition contract.
A closed composite stores a new disposer for an unreachable future close · case 03
A closed composite stores a new disposer for an unreachable future close; the returned lifecycle plan violates the stated transition contract.
A closed composite stores a new disposer for an unreachable future close · case 04
A closed composite stores a new disposer for an unreachable future close; the returned lifecycle plan violates the stated transition contract.
A closed composite stores a new disposer for an unreachable future close · case 05
A closed composite stores a new disposer for an unreachable future close; the returned lifecycle plan violates the stated transition contract.
Ownership transfer disposes the transferred listener resource · case 01
Ownership transfer disposes the transferred listener resource; the returned lifecycle plan violates the stated transition contract.
Ownership transfer disposes the transferred listener resource · case 02
Ownership transfer disposes the transferred listener resource; the returned lifecycle plan violates the stated transition contract.
Ownership transfer disposes the transferred listener resource · case 03
Ownership transfer disposes the transferred listener resource; the returned lifecycle plan violates the stated transition contract.
Ownership transfer disposes the transferred listener resource · case 04
Ownership transfer disposes the transferred listener resource; the returned lifecycle plan violates the stated transition contract.
Ownership transfer disposes the transferred listener resource · case 05
Ownership transfer disposes the transferred listener resource; the returned lifecycle plan violates the stated transition contract.
Transferring one disposer removes every disposer from the composite · case 01
Transferring one disposer removes every disposer from the composite; the returned lifecycle plan violates the stated transition contract.
Transferring one disposer removes every disposer from the composite · case 02
Transferring one disposer removes every disposer from the composite; the returned lifecycle plan violates the stated transition contract.
Transferring one disposer removes every disposer from the composite · case 03
Transferring one disposer removes every disposer from the composite; the returned lifecycle plan violates the stated transition contract.
Transferring one disposer removes every disposer from the composite · case 04
Transferring one disposer removes every disposer from the composite; the returned lifecycle plan violates the stated transition contract.
Transferring one disposer removes every disposer from the composite · case 05
Transferring one disposer removes every disposer from the composite; the returned lifecycle plan violates the stated transition contract.
A disposer alias hides an earlier completed execution · case 01
A disposer alias hides an earlier completed execution; the returned lifecycle plan violates the stated transition contract.
A disposer alias hides an earlier completed execution · case 02
A disposer alias hides an earlier completed execution; the returned lifecycle plan violates the stated transition contract.
A disposer alias hides an earlier completed execution · case 03
A disposer alias hides an earlier completed execution; the returned lifecycle plan violates the stated transition contract.
A disposer alias hides an earlier completed execution · case 04
A disposer alias hides an earlier completed execution; the returned lifecycle plan violates the stated transition contract.
A disposer alias hides an earlier completed execution · case 05
A disposer alias hides an earlier completed execution; the returned lifecycle plan violates the stated transition contract.
Composite teardown reports only the last cleanup exception · case 01
Composite teardown reports only the last cleanup exception; the returned lifecycle plan violates the stated transition contract.
Composite teardown reports only the last cleanup exception · case 02
Composite teardown reports only the last cleanup exception; the returned lifecycle plan violates the stated transition contract.
Composite teardown reports only the last cleanup exception · case 03
Composite teardown reports only the last cleanup exception; the returned lifecycle plan violates the stated transition contract.
Composite teardown reports only the last cleanup exception · case 04
Composite teardown reports only the last cleanup exception; the returned lifecycle plan violates the stated transition contract.
Composite teardown reports only the last cleanup exception · case 05
Composite teardown reports only the last cleanup exception; the returned lifecycle plan violates the stated transition contract.
Disposers registered during teardown interrupt the current disposal wave · case 01
Disposers registered during teardown interrupt the current disposal wave; the returned lifecycle plan violates the stated transition contract.
Disposers registered during teardown interrupt the current disposal wave · case 02
Disposers registered during teardown interrupt the current disposal wave; the returned lifecycle plan violates the stated transition contract.
Disposers registered during teardown interrupt the current disposal wave · case 03
Disposers registered during teardown interrupt the current disposal wave; the returned lifecycle plan violates the stated transition contract.
Disposers registered during teardown interrupt the current disposal wave · case 04
Disposers registered during teardown interrupt the current disposal wave; the returned lifecycle plan violates the stated transition contract.
Disposers registered during teardown interrupt the current disposal wave · case 05
Disposers registered during teardown interrupt the current disposal wave; the returned lifecycle plan violates the stated transition contract.
Ownership transfer leaves the disposer attributed to its old scope · case 01
Ownership transfer leaves the disposer attributed to its old scope; the returned lifecycle plan violates the stated transition contract.
Ownership transfer leaves the disposer attributed to its old scope · case 02
Ownership transfer leaves the disposer attributed to its old scope; the returned lifecycle plan violates the stated transition contract.
Ownership transfer leaves the disposer attributed to its old scope · case 03
Ownership transfer leaves the disposer attributed to its old scope; the returned lifecycle plan violates the stated transition contract.
Ownership transfer leaves the disposer attributed to its old scope · case 04
Ownership transfer leaves the disposer attributed to its old scope; the returned lifecycle plan violates the stated transition contract.
Ownership transfer leaves the disposer attributed to its old scope · case 05
Ownership transfer leaves the disposer attributed to its old scope; the returned lifecycle plan violates the stated transition contract.
Teardown transfer retains callbacks capturing the relinquished owner · case 01
Teardown transfer retains callbacks capturing the relinquished owner; the returned lifecycle plan violates the stated transition contract.
Teardown transfer retains callbacks capturing the relinquished owner · case 02
Teardown transfer retains callbacks capturing the relinquished owner; the returned lifecycle plan violates the stated transition contract.
Teardown transfer retains callbacks capturing the relinquished owner · case 03
Teardown transfer retains callbacks capturing the relinquished owner; the returned lifecycle plan violates the stated transition contract.
Teardown transfer retains callbacks capturing the relinquished owner · case 04
Teardown transfer retains callbacks capturing the relinquished owner; the returned lifecycle plan violates the stated transition contract.
Teardown transfer retains callbacks capturing the relinquished owner · case 05
Teardown transfer retains callbacks capturing the relinquished owner; the returned lifecycle plan violates the stated transition contract.
Nested callback receiver restoration ignores completed inner frames · case 01
Nested callback receiver restoration ignores completed inner frames; the returned lifecycle plan violates the stated transition contract.
Nested callback receiver restoration ignores completed inner frames · case 02
Nested callback receiver restoration ignores completed inner frames; the returned lifecycle plan violates the stated transition contract.
Nested callback receiver restoration ignores completed inner frames · case 03
Nested callback receiver restoration ignores completed inner frames; the returned lifecycle plan violates the stated transition contract.
Nested callback receiver restoration ignores completed inner frames · case 04
Nested callback receiver restoration ignores completed inner frames; the returned lifecycle plan violates the stated transition contract.
Nested callback receiver restoration ignores completed inner frames · case 05
Nested callback receiver restoration ignores completed inner frames; the returned lifecycle plan violates the stated transition contract.
Explicit None receiver is treated as an absent callback binding · case 01
Explicit None receiver is treated as an absent callback binding; the returned lifecycle plan violates the stated transition contract.
Explicit None receiver is treated as an absent callback binding · case 02
Explicit None receiver is treated as an absent callback binding; the returned lifecycle plan violates the stated transition contract.
Explicit None receiver is treated as an absent callback binding · case 03
Explicit None receiver is treated as an absent callback binding; the returned lifecycle plan violates the stated transition contract.
Explicit None receiver is treated as an absent callback binding · case 04
Explicit None receiver is treated as an absent callback binding; the returned lifecycle plan violates the stated transition contract.
Explicit None receiver is treated as an absent callback binding · case 05
Explicit None receiver is treated as an absent callback binding; the returned lifecycle plan violates the stated transition contract.
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 ↗