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
Throttle leading policy permits two leading callbacks · case 01
Throttle leading policy permits two leading callbacks; the returned lifecycle plan violates the stated transition contract.
Throttle leading policy permits two leading callbacks · case 02
Throttle leading policy permits two leading callbacks; the returned lifecycle plan violates the stated transition contract.
Throttle leading policy permits two leading callbacks · case 03
Throttle leading policy permits two leading callbacks; the returned lifecycle plan violates the stated transition contract.
Throttle leading policy permits two leading callbacks · case 04
Throttle leading policy permits two leading callbacks; the returned lifecycle plan violates the stated transition contract.
Throttle leading policy permits two leading callbacks · case 05
Throttle leading policy permits two leading callbacks; the returned lifecycle plan violates the stated transition contract.
Throttle trailing callback replays the first suppressed value · case 01
Throttle trailing callback replays the first suppressed value; the returned lifecycle plan violates the stated transition contract.
Throttle trailing callback replays the first suppressed value · case 02
Throttle trailing callback replays the first suppressed value; the returned lifecycle plan violates the stated transition contract.
Throttle trailing callback replays the first suppressed value · case 03
Throttle trailing callback replays the first suppressed value; the returned lifecycle plan violates the stated transition contract.
Throttle trailing callback replays the first suppressed value · case 04
Throttle trailing callback replays the first suppressed value; the returned lifecycle plan violates the stated transition contract.
Throttle trailing callback replays the first suppressed value · case 05
Throttle trailing callback replays the first suppressed value; the returned lifecycle plan violates the stated transition contract.
Throttle expiry flushes when trailing policy is disabled · case 01
Throttle expiry flushes when trailing policy is disabled; the returned lifecycle plan violates the stated transition contract.
Throttle expiry flushes when trailing policy is disabled · case 02
Throttle expiry flushes when trailing policy is disabled; the returned lifecycle plan violates the stated transition contract.
Throttle expiry flushes when trailing policy is disabled · case 03
Throttle expiry flushes when trailing policy is disabled; the returned lifecycle plan violates the stated transition contract.
Throttle expiry flushes when trailing policy is disabled · case 04
Throttle expiry flushes when trailing policy is disabled; the returned lifecycle plan violates the stated transition contract.
Throttle expiry flushes when trailing policy is disabled · case 05
Throttle expiry flushes when trailing policy is disabled; the returned lifecycle plan violates the stated transition contract.
A trailing-only throttle consumes the leading delivery slot · case 01
A trailing-only throttle consumes the leading delivery slot; the returned lifecycle plan violates the stated transition contract.
A trailing-only throttle consumes the leading delivery slot · case 02
A trailing-only throttle consumes the leading delivery slot; the returned lifecycle plan violates the stated transition contract.
A trailing-only throttle consumes the leading delivery slot · case 03
A trailing-only throttle consumes the leading delivery slot; the returned lifecycle plan violates the stated transition contract.
A trailing-only throttle consumes the leading delivery slot · case 04
A trailing-only throttle consumes the leading delivery slot; the returned lifecycle plan violates the stated transition contract.
A trailing-only throttle consumes the leading delivery slot · case 05
A trailing-only throttle consumes the leading delivery slot; the returned lifecycle plan violates the stated transition contract.
Trailing-only throttle drops its opening event · case 01
Trailing-only throttle drops its opening event; the returned lifecycle plan violates the stated transition contract.
Trailing-only throttle drops its opening event · case 02
Trailing-only throttle drops its opening event; the returned lifecycle plan violates the stated transition contract.
Trailing-only throttle drops its opening event · case 03
Trailing-only throttle drops its opening event; the returned lifecycle plan violates the stated transition contract.
Trailing-only throttle drops its opening event · case 04
Trailing-only throttle drops its opening event; the returned lifecycle plan violates the stated transition contract.
Trailing-only throttle drops its opening event · case 05
Trailing-only throttle drops its opening event; the returned lifecycle plan violates the stated transition contract.
Throttle timer delay becomes negative after a late callback · case 01
Throttle timer delay becomes negative after a late callback; the returned lifecycle plan violates the stated transition contract.
Throttle timer delay becomes negative after a late callback · case 02
Throttle timer delay becomes negative after a late callback; the returned lifecycle plan violates the stated transition contract.
Throttle timer delay becomes negative after a late callback · case 03
Throttle timer delay becomes negative after a late callback; the returned lifecycle plan violates the stated transition contract.
Throttle timer delay becomes negative after a late callback · case 04
Throttle timer delay becomes negative after a late callback; the returned lifecycle plan violates the stated transition contract.
Throttle timer delay becomes negative after a late callback · case 05
Throttle timer delay becomes negative after a late callback; the returned lifecycle plan violates the stated transition contract.
Trailing throttle delivery repeats the already delivered leading sequence · case 01
Trailing throttle delivery repeats the already delivered leading sequence; the returned lifecycle plan violates the stated transition contract.
Trailing throttle delivery repeats the already delivered leading sequence · case 02
Trailing throttle delivery repeats the already delivered leading sequence; the returned lifecycle plan violates the stated transition contract.
Trailing throttle delivery repeats the already delivered leading sequence · case 03
Trailing throttle delivery repeats the already delivered leading sequence; the returned lifecycle plan violates the stated transition contract.
Trailing throttle delivery repeats the already delivered leading sequence · case 04
Trailing throttle delivery repeats the already delivered leading sequence; the returned lifecycle plan violates the stated transition contract.
Trailing throttle delivery repeats the already delivered leading sequence · case 05
Trailing throttle delivery repeats the already delivered leading sequence; the returned lifecycle plan violates the stated transition contract.
Throttle drop reporting counts absent events as suppressed · case 01
Throttle drop reporting counts absent events as suppressed; the returned lifecycle plan violates the stated transition contract.
Throttle drop reporting counts absent events as suppressed · case 02
Throttle drop reporting counts absent events as suppressed; the returned lifecycle plan violates the stated transition contract.
Throttle drop reporting counts absent events as suppressed · case 03
Throttle drop reporting counts absent events as suppressed; the returned lifecycle plan violates the stated transition contract.
Throttle drop reporting counts absent events as suppressed · case 04
Throttle drop reporting counts absent events as suppressed; the returned lifecycle plan violates the stated transition contract.
Throttle drop reporting counts absent events as suppressed · case 05
Throttle drop reporting counts absent events as suppressed; the returned lifecycle plan violates the stated transition contract.
Repeated invalidation produces duplicate observer field callbacks · case 01
Repeated invalidation produces duplicate observer field callbacks; the returned lifecycle plan violates the stated transition contract.
Repeated invalidation produces duplicate observer field callbacks · case 02
Repeated invalidation produces duplicate observer field callbacks; the returned lifecycle plan violates the stated transition contract.
Repeated invalidation produces duplicate observer field callbacks · case 03
Repeated invalidation produces duplicate observer field callbacks; the returned lifecycle plan violates the stated transition contract.
Repeated invalidation produces duplicate observer field callbacks · case 04
Repeated invalidation produces duplicate observer field callbacks; the returned lifecycle plan violates the stated transition contract.
Repeated invalidation produces duplicate observer field callbacks · case 05
Repeated invalidation produces duplicate observer field callbacks; the returned lifecycle plan violates the stated transition contract.
Each invalidation creates another microtask while one is scheduled · case 01
Each invalidation creates another microtask while one is scheduled; the returned lifecycle plan violates the stated transition contract.
Each invalidation creates another microtask while one is scheduled · case 02
Each invalidation creates another microtask while one is scheduled; the returned lifecycle plan violates the stated transition contract.
Each invalidation creates another microtask while one is scheduled · case 03
Each invalidation creates another microtask while one is scheduled; the returned lifecycle plan violates the stated transition contract.
Each invalidation creates another microtask while one is scheduled · case 04
Each invalidation creates another microtask while one is scheduled; the returned lifecycle plan violates the stated transition contract.
Each invalidation creates another microtask while one is scheduled · case 05
Each invalidation creates another microtask while one is scheduled; the returned lifecycle plan violates the stated transition contract.
Callback-time dirt is merged into the currently executing batch · case 01
Callback-time dirt is merged into the currently executing batch; the returned lifecycle plan violates the stated transition contract.
Callback-time dirt is merged into the currently executing batch · case 02
Callback-time dirt is merged into the currently executing batch; the returned lifecycle plan violates the stated transition contract.
Callback-time dirt is merged into the currently executing batch · case 03
Callback-time dirt is merged into the currently executing batch; the returned lifecycle plan violates the stated transition contract.
Callback-time dirt is merged into the currently executing batch · case 04
Callback-time dirt is merged into the currently executing batch; the returned lifecycle plan violates the stated transition contract.
Callback-time dirt is merged into the currently executing batch · case 05
Callback-time dirt is merged into the currently executing batch; the returned lifecycle plan violates the stated transition contract.
A flush clears invalidations generated by its own callbacks · case 01
A flush clears invalidations generated by its own callbacks; the returned lifecycle plan violates the stated transition contract.
A flush clears invalidations generated by its own callbacks · case 02
A flush clears invalidations generated by its own callbacks; the returned lifecycle plan violates the stated transition contract.
A flush clears invalidations generated by its own callbacks · case 03
A flush clears invalidations generated by its own callbacks; the returned lifecycle plan violates the stated transition contract.
A flush clears invalidations generated by its own callbacks · case 04
A flush clears invalidations generated by its own callbacks; the returned lifecycle plan violates the stated transition contract.
A flush clears invalidations generated by its own callbacks · case 05
A flush clears invalidations generated by its own callbacks; the returned lifecycle plan violates the stated transition contract.
Field-level filtering hides a full observer invalidation · case 01
Field-level filtering hides a full observer invalidation; the returned lifecycle plan violates the stated transition contract.
Field-level filtering hides a full observer invalidation · case 02
Field-level filtering hides a full observer invalidation; the returned lifecycle plan violates the stated transition contract.
Field-level filtering hides a full observer invalidation · case 03
Field-level filtering hides a full observer invalidation; the returned lifecycle plan violates the stated transition contract.
Field-level filtering hides a full observer invalidation · case 04
Field-level filtering hides a full observer invalidation; the returned lifecycle plan violates the stated transition contract.
Field-level filtering hides a full observer invalidation · case 05
Field-level filtering hides a full observer invalidation; the returned lifecycle plan violates the stated transition contract.
A no-op flush advances invalidation version · case 01
A no-op flush advances invalidation version; the returned lifecycle plan violates the stated transition contract.
A no-op flush advances invalidation version · case 02
A no-op flush advances invalidation version; the returned lifecycle plan violates the stated transition contract.
A no-op flush advances invalidation version · case 03
A no-op flush advances invalidation version; the returned lifecycle plan violates the stated transition contract.
A no-op flush advances invalidation version · case 04
A no-op flush advances invalidation version; the returned lifecycle plan violates the stated transition contract.
A no-op flush advances invalidation version · case 05
A no-op flush advances invalidation version; the returned lifecycle plan violates the stated transition contract.
Microtask scheduled marker remains set after an empty flush · case 01
Microtask scheduled marker remains set after an empty flush; the returned lifecycle plan violates the stated transition contract.
Microtask scheduled marker remains set after an empty flush · case 02
Microtask scheduled marker remains set after an empty flush; the returned lifecycle plan violates the stated transition contract.
Microtask scheduled marker remains set after an empty flush · case 03
Microtask scheduled marker remains set after an empty flush; the returned lifecycle plan violates the stated transition contract.
Microtask scheduled marker remains set after an empty flush · case 04
Microtask scheduled marker remains set after an empty flush; the returned lifecycle plan violates the stated transition contract.
Microtask scheduled marker remains set after an empty flush · case 05
Microtask scheduled marker remains set after an empty flush; the returned lifecycle plan violates the stated transition contract.
Invalidation freshness compares against the wrong generation direction · case 01
Invalidation freshness compares against the wrong generation direction; the returned lifecycle plan violates the stated transition contract.
Invalidation freshness compares against the wrong generation direction · case 02
Invalidation freshness compares against the wrong generation direction; the returned lifecycle plan violates the stated transition contract.
Invalidation freshness compares against the wrong generation direction · case 03
Invalidation freshness compares against the wrong generation direction; the returned lifecycle plan violates the stated transition contract.
Invalidation freshness compares against the wrong generation direction · case 04
Invalidation freshness compares against the wrong generation direction; the returned lifecycle plan violates the stated transition contract.
Invalidation freshness compares against the wrong generation direction · case 05
Invalidation freshness compares against the wrong generation direction; the returned lifecycle plan violates the stated transition contract.
Coalesced observer flush recursively enters an active flush · case 01
Coalesced observer flush recursively enters an active flush; the returned lifecycle plan violates the stated transition contract.
Coalesced observer flush recursively enters an active flush · case 02
Coalesced observer flush recursively enters an active flush; the returned lifecycle plan violates the stated transition contract.
Coalesced observer flush recursively enters an active flush · case 03
Coalesced observer flush recursively enters an active flush; the returned lifecycle plan violates the stated transition contract.
Coalesced observer flush recursively enters an active flush · case 04
Coalesced observer flush recursively enters an active flush; the returned lifecycle plan violates the stated transition contract.
Coalesced observer flush recursively enters an active flush · case 05
Coalesced observer flush recursively enters an active flush; the returned lifecycle plan violates the stated transition contract.
Disposed invalidation observer retains dirty field names · case 01
Disposed invalidation observer retains dirty field names; the returned lifecycle plan violates the stated transition contract.
Disposed invalidation observer retains dirty field names · case 02
Disposed invalidation observer retains dirty field names; the returned lifecycle plan violates the stated transition contract.
Disposed invalidation observer retains dirty field names · case 03
Disposed invalidation observer retains dirty field names; the returned lifecycle plan violates the stated transition contract.
Disposed invalidation observer retains dirty field names · case 04
Disposed invalidation observer retains dirty field names; the returned lifecycle plan violates the stated transition contract.
Disposed invalidation observer retains dirty field names · case 05
Disposed invalidation observer retains dirty field names; the returned lifecycle plan violates the stated transition contract.
Observer batches publish before their threshold is reached · case 01
Observer batches publish before their threshold is reached; the returned lifecycle plan violates the stated transition contract.
Observer batches publish before their threshold is reached · case 02
Observer batches publish before their threshold is reached; the returned lifecycle plan violates the stated transition contract.
Observer batches publish before their threshold is reached · case 03
Observer batches publish before their threshold is reached; the returned lifecycle plan violates the stated transition contract.
Observer batches publish before their threshold is reached · case 04
Observer batches publish before their threshold is reached; the returned lifecycle plan violates the stated transition contract.
Observer batches publish before their threshold is reached · case 05
Observer batches publish before their threshold is reached; the returned lifecycle plan violates the stated transition contract.
Nested batching publishes an inner batch immediately · case 01
Nested batching publishes an inner batch immediately; the returned lifecycle plan violates the stated transition contract.
Nested batching publishes an inner batch immediately · case 02
Nested batching publishes an inner batch immediately; the returned lifecycle plan violates the stated transition contract.
Nested batching publishes an inner batch immediately · case 03
Nested batching publishes an inner batch immediately; the returned lifecycle plan violates the stated transition contract.
Nested batching publishes an inner batch immediately · case 04
Nested batching publishes an inner batch immediately; the returned lifecycle plan violates the stated transition contract.
Nested batching publishes an inner batch immediately · case 05
Nested batching publishes an inner batch immediately; 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 ↗