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
Batch publication takes records from the end of the pending batch · case 01
Batch publication takes records from the end of the pending batch; the returned lifecycle plan violates the stated transition contract.
Batch publication takes records from the end of the pending batch · case 02
Batch publication takes records from the end of the pending batch; the returned lifecycle plan violates the stated transition contract.
Batch publication takes records from the end of the pending batch · case 03
Batch publication takes records from the end of the pending batch; the returned lifecycle plan violates the stated transition contract.
Batch publication takes records from the end of the pending batch · case 04
Batch publication takes records from the end of the pending batch; the returned lifecycle plan violates the stated transition contract.
Batch publication takes records from the end of the pending batch · case 05
Batch publication takes records from the end of the pending batch; the returned lifecycle plan violates the stated transition contract.
Batch publication discards the first record of the next batch · case 01
Batch publication discards the first record of the next batch; the returned lifecycle plan violates the stated transition contract.
Batch publication discards the first record of the next batch · case 02
Batch publication discards the first record of the next batch; the returned lifecycle plan violates the stated transition contract.
Batch publication discards the first record of the next batch · case 03
Batch publication discards the first record of the next batch; the returned lifecycle plan violates the stated transition contract.
Batch publication discards the first record of the next batch · case 04
Batch publication discards the first record of the next batch; the returned lifecycle plan violates the stated transition contract.
Batch publication discards the first record of the next batch · case 05
Batch publication discards the first record of the next batch; the returned lifecycle plan violates the stated transition contract.
Batch callback failure removes events before its checkpoint · case 01
Batch callback failure removes events before its checkpoint; the returned lifecycle plan violates the stated transition contract.
Batch callback failure removes events before its checkpoint · case 02
Batch callback failure removes events before its checkpoint; the returned lifecycle plan violates the stated transition contract.
Batch callback failure removes events before its checkpoint · case 03
Batch callback failure removes events before its checkpoint; the returned lifecycle plan violates the stated transition contract.
Batch callback failure removes events before its checkpoint · case 04
Batch callback failure removes events before its checkpoint; the returned lifecycle plan violates the stated transition contract.
Batch callback failure removes events before its checkpoint · case 05
Batch callback failure removes events before its checkpoint; the returned lifecycle plan violates the stated transition contract.
Ending a nonexistent observer batch produces negative nesting · case 01
Ending a nonexistent observer batch produces negative nesting; the returned lifecycle plan violates the stated transition contract.
Ending a nonexistent observer batch produces negative nesting · case 02
Ending a nonexistent observer batch produces negative nesting; the returned lifecycle plan violates the stated transition contract.
Ending a nonexistent observer batch produces negative nesting · case 03
Ending a nonexistent observer batch produces negative nesting; the returned lifecycle plan violates the stated transition contract.
Ending a nonexistent observer batch produces negative nesting · case 04
Ending a nonexistent observer batch produces negative nesting; the returned lifecycle plan violates the stated transition contract.
Ending a nonexistent observer batch produces negative nesting · case 05
Ending a nonexistent observer batch produces negative nesting; the returned lifecycle plan violates the stated transition contract.
Incomplete final batches are dropped despite partial-delivery policy · case 01
Incomplete final batches are dropped despite partial-delivery policy; the returned lifecycle plan violates the stated transition contract.
Incomplete final batches are dropped despite partial-delivery policy · case 02
Incomplete final batches are dropped despite partial-delivery policy; the returned lifecycle plan violates the stated transition contract.
Incomplete final batches are dropped despite partial-delivery policy · case 03
Incomplete final batches are dropped despite partial-delivery policy; the returned lifecycle plan violates the stated transition contract.
Incomplete final batches are dropped despite partial-delivery policy · case 04
Incomplete final batches are dropped despite partial-delivery policy; the returned lifecycle plan violates the stated transition contract.
Incomplete final batches are dropped despite partial-delivery policy · case 05
Incomplete final batches are dropped despite partial-delivery policy; the returned lifecycle plan violates the stated transition contract.
Beginning an inner batch overwrites its checkpoint with zero · case 01
Beginning an inner batch overwrites its checkpoint with zero; the returned lifecycle plan violates the stated transition contract.
Beginning an inner batch overwrites its checkpoint with zero · case 02
Beginning an inner batch overwrites its checkpoint with zero; the returned lifecycle plan violates the stated transition contract.
Beginning an inner batch overwrites its checkpoint with zero · case 03
Beginning an inner batch overwrites its checkpoint with zero; the returned lifecycle plan violates the stated transition contract.
Beginning an inner batch overwrites its checkpoint with zero · case 04
Beginning an inner batch overwrites its checkpoint with zero; the returned lifecycle plan violates the stated transition contract.
Beginning an inner batch overwrites its checkpoint with zero · case 05
Beginning an inner batch overwrites its checkpoint with zero; the returned lifecycle plan violates the stated transition contract.
A valid nested batch end is reported as unmatched · case 01
A valid nested batch end is reported as unmatched; the returned lifecycle plan violates the stated transition contract.
A valid nested batch end is reported as unmatched · case 02
A valid nested batch end is reported as unmatched; the returned lifecycle plan violates the stated transition contract.
A valid nested batch end is reported as unmatched · case 03
A valid nested batch end is reported as unmatched; the returned lifecycle plan violates the stated transition contract.
A valid nested batch end is reported as unmatched · case 04
A valid nested batch end is reported as unmatched; the returned lifecycle plan violates the stated transition contract.
A valid nested batch end is reported as unmatched · case 05
A valid nested batch end is reported as unmatched; the returned lifecycle plan violates the stated transition contract.
Batch acknowledgements repeat an already acknowledged notification batch · case 01
Batch acknowledgements repeat an already acknowledged notification batch; the returned lifecycle plan violates the stated transition contract.
Batch acknowledgements repeat an already acknowledged notification batch · case 02
Batch acknowledgements repeat an already acknowledged notification batch; the returned lifecycle plan violates the stated transition contract.
Batch acknowledgements repeat an already acknowledged notification batch · case 03
Batch acknowledgements repeat an already acknowledged notification batch; the returned lifecycle plan violates the stated transition contract.
Batch acknowledgements repeat an already acknowledged notification batch · case 04
Batch acknowledgements repeat an already acknowledged notification batch; the returned lifecycle plan violates the stated transition contract.
Batch acknowledgements repeat an already acknowledged notification batch · case 05
Batch acknowledgements repeat an already acknowledged notification batch; the returned lifecycle plan violates the stated transition contract.
Observers see transaction changes before commit · case 01
Observers see transaction changes before commit; the returned lifecycle plan violates the stated transition contract.
Observers see transaction changes before commit · case 02
Observers see transaction changes before commit; the returned lifecycle plan violates the stated transition contract.
Observers see transaction changes before commit · case 03
Observers see transaction changes before commit; the returned lifecycle plan violates the stated transition contract.
Observers see transaction changes before commit · case 04
Observers see transaction changes before commit; the returned lifecycle plan violates the stated transition contract.
Observers see transaction changes before commit · case 05
Observers see transaction changes before commit; the returned lifecycle plan violates the stated transition contract.
No-op field assignments produce change notifications · case 01
No-op field assignments produce change notifications; the returned lifecycle plan violates the stated transition contract.
No-op field assignments produce change notifications · case 02
No-op field assignments produce change notifications; the returned lifecycle plan violates the stated transition contract.
No-op field assignments produce change notifications · case 03
No-op field assignments produce change notifications; the returned lifecycle plan violates the stated transition contract.
No-op field assignments produce change notifications · case 04
No-op field assignments produce change notifications; the returned lifecycle plan violates the stated transition contract.
No-op field assignments produce change notifications · case 05
No-op field assignments produce change notifications; the returned lifecycle plan violates the stated transition contract.
Transaction coalescing records the last prior field value · case 01
Transaction coalescing records the last prior field value; the returned lifecycle plan violates the stated transition contract.
Transaction coalescing records the last prior field value · case 02
Transaction coalescing records the last prior field value; the returned lifecycle plan violates the stated transition contract.
Transaction coalescing records the last prior field value · case 03
Transaction coalescing records the last prior field value; the returned lifecycle plan violates the stated transition contract.
Transaction coalescing records the last prior field value · case 04
Transaction coalescing records the last prior field value; the returned lifecycle plan violates the stated transition contract.
Transaction coalescing records the last prior field value · case 05
Transaction coalescing records the last prior field value; the returned lifecycle plan violates the stated transition contract.
Transaction coalescing retains the first intermediate new value · case 01
Transaction coalescing retains the first intermediate new value; the returned lifecycle plan violates the stated transition contract.
Transaction coalescing retains the first intermediate new value · case 02
Transaction coalescing retains the first intermediate new value; the returned lifecycle plan violates the stated transition contract.
Transaction coalescing retains the first intermediate new value · case 03
Transaction coalescing retains the first intermediate new value; the returned lifecycle plan violates the stated transition contract.
Transaction coalescing retains the first intermediate new value · case 04
Transaction coalescing retains the first intermediate new value; the returned lifecycle plan violates the stated transition contract.
Transaction coalescing retains the first intermediate new value · case 05
Transaction coalescing retains the first intermediate new value; the returned lifecycle plan violates the stated transition contract.
Transaction notification order is reversed after coalescing · case 01
Transaction notification order is reversed after coalescing; the returned lifecycle plan violates the stated transition contract.
Transaction notification order is reversed after coalescing · case 02
Transaction notification order is reversed after coalescing; the returned lifecycle plan violates the stated transition contract.
Transaction notification order is reversed after coalescing · case 03
Transaction notification order is reversed after coalescing; the returned lifecycle plan violates the stated transition contract.
Transaction notification order is reversed after coalescing · case 04
Transaction notification order is reversed after coalescing; the returned lifecycle plan violates the stated transition contract.
Transaction notification order is reversed after coalescing · case 05
Transaction notification order is reversed after coalescing; the returned lifecycle plan violates the stated transition contract.
Rollback publishes the tentative transaction revision · case 01
Rollback publishes the tentative transaction revision; the returned lifecycle plan violates the stated transition contract.
Rollback publishes the tentative transaction revision · case 02
Rollback publishes the tentative transaction revision; the returned lifecycle plan violates the stated transition contract.
Rollback publishes the tentative transaction revision · case 03
Rollback publishes the tentative transaction revision; the returned lifecycle plan violates the stated transition contract.
Rollback publishes the tentative transaction revision · case 04
Rollback publishes the tentative transaction revision; the returned lifecycle plan violates the stated transition contract.
Rollback publishes the tentative transaction revision · case 05
Rollback publishes the tentative transaction revision; the returned lifecycle plan violates the stated transition contract.
An observer exception rolls back an already committed transaction · case 01
An observer exception rolls back an already committed transaction; the returned lifecycle plan violates the stated transition contract.
An observer exception rolls back an already committed transaction · case 02
An observer exception rolls back an already committed transaction; the returned lifecycle plan violates the stated transition contract.
An observer exception rolls back an already committed transaction · case 03
An observer exception rolls back an already committed transaction; the returned lifecycle plan violates the stated transition contract.
An observer exception rolls back an already committed transaction · case 04
An observer exception rolls back an already committed transaction; the returned lifecycle plan violates the stated transition contract.
An observer exception rolls back an already committed transaction · case 05
An observer exception rolls back an already committed transaction; the returned lifecycle plan violates the stated transition contract.
Committed observer error reporting follows arrival order instead of observer order · case 01
Committed observer error reporting follows arrival order instead of observer order; the returned lifecycle plan violates the stated transition contract.
Committed observer error reporting follows arrival order instead of observer order · case 02
Committed observer error reporting follows arrival order instead of observer order; the returned lifecycle plan violates the stated transition contract.
Committed observer error reporting follows arrival order instead of observer order · case 03
Committed observer error reporting follows arrival order instead of observer order; the returned lifecycle plan violates the stated transition contract.
Committed observer error reporting follows arrival order instead of observer order · case 04
Committed observer error reporting follows arrival order instead of observer order; the returned lifecycle plan violates the stated transition contract.
Committed observer error reporting follows arrival order instead of observer order · case 05
Committed observer error reporting follows arrival order instead of observer order; the returned lifecycle plan violates the stated transition contract.
Durability-required observers run before durable commit · case 01
Durability-required observers run before durable commit; the returned lifecycle plan violates the stated transition contract.
Durability-required observers run before durable commit · case 02
Durability-required observers run before durable commit; the returned lifecycle plan violates the stated transition contract.
Durability-required observers run before durable commit · case 03
Durability-required observers run before durable commit; the returned lifecycle plan violates the stated transition contract.
Durability-required observers run before durable commit · case 04
Durability-required observers run before durable commit; the returned lifecycle plan violates the stated transition contract.
Durability-required observers run before durable commit · case 05
Durability-required observers run before durable commit; the returned lifecycle plan violates the stated transition contract.
Rolling back an inner savepoint erases its parent observer changes · case 01
Rolling back an inner savepoint erases its parent observer changes; the returned lifecycle plan violates the stated transition contract.
Rolling back an inner savepoint erases its parent observer changes · case 02
Rolling back an inner savepoint erases its parent observer changes; the returned lifecycle plan violates the stated transition contract.
Rolling back an inner savepoint erases its parent observer changes · case 03
Rolling back an inner savepoint erases its parent observer changes; the returned lifecycle plan violates the stated transition contract.
Rolling back an inner savepoint erases its parent observer changes · case 04
Rolling back an inner savepoint erases its parent observer changes; the returned lifecycle plan violates the stated transition contract.
Rolling back an inner savepoint erases its parent observer changes · case 05
Rolling back an inner savepoint erases its parent observer changes; the returned lifecycle plan violates the stated transition contract.
An older asynchronous callback overwrites a newer listener result · case 01
An older asynchronous callback overwrites a newer listener result; the returned lifecycle plan violates the stated transition contract.
An older asynchronous callback overwrites a newer listener result · case 02
An older asynchronous callback overwrites a newer listener result; the returned lifecycle plan violates the stated transition contract.
An older asynchronous callback overwrites a newer listener result · case 03
An older asynchronous callback overwrites a newer listener result; the returned lifecycle plan violates the stated transition contract.
An older asynchronous callback overwrites a newer listener result · case 04
An older asynchronous callback overwrites a newer listener result; the returned lifecycle plan violates the stated transition contract.
An older asynchronous callback overwrites a newer listener result · case 05
An older asynchronous callback overwrites a newer listener result; the returned lifecycle plan violates the stated transition contract.
Async callback rejection is delivered twice on duplicate settlement · case 01
Async callback rejection is delivered twice on duplicate settlement; the returned lifecycle plan violates the stated transition contract.
Async callback rejection is delivered twice on duplicate settlement · case 02
Async callback rejection is delivered twice on duplicate settlement; the returned lifecycle plan violates the stated transition contract.
Async callback rejection is delivered twice on duplicate settlement · case 03
Async callback rejection is delivered twice on duplicate settlement; the returned lifecycle plan violates the stated transition contract.
Async callback rejection is delivered twice on duplicate settlement · case 04
Async callback rejection is delivered twice on duplicate settlement; the returned lifecycle plan violates the stated transition contract.
Async callback rejection is delivered twice on duplicate settlement · case 05
Async callback rejection is delivered twice on duplicate settlement; 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 ↗