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
Peer configuration epoch activation controller: pending / invalid · case 01
While pending, event invalid produces prepared/send_prepared instead of active/discard_proposal.
Peer configuration epoch activation controller: pending / invalid · case 02
While pending, event invalid produces prepared/send_prepared instead of active/discard_proposal.
Peer configuration epoch activation controller: pending / invalid · case 03
While pending, event invalid produces prepared/send_prepared instead of active/discard_proposal.
Peer configuration epoch activation controller: pending / invalid · case 04
While pending, event invalid produces prepared/send_prepared instead of active/discard_proposal.
Peer configuration epoch activation controller: pending / invalid · case 05
While pending, event invalid produces prepared/send_prepared instead of active/discard_proposal.
Peer configuration epoch activation controller: prepared / activate · case 01
While prepared, event activate produces prepared/wait instead of active/swap_epoch.
Peer configuration epoch activation controller: prepared / activate · case 02
While prepared, event activate produces prepared/wait instead of active/swap_epoch.
Peer configuration epoch activation controller: prepared / activate · case 03
While prepared, event activate produces prepared/wait instead of active/swap_epoch.
Peer configuration epoch activation controller: prepared / activate · case 04
While prepared, event activate produces prepared/wait instead of active/swap_epoch.
Peer configuration epoch activation controller: prepared / activate · case 05
While prepared, event activate produces prepared/wait instead of active/swap_epoch.
Peer configuration epoch activation controller: prepared / withdraw · case 01
While prepared, event withdraw produces active/swap_epoch instead of active/discard_proposal.
Peer configuration epoch activation controller: prepared / withdraw · case 02
While prepared, event withdraw produces active/swap_epoch instead of active/discard_proposal.
Peer configuration epoch activation controller: prepared / withdraw · case 03
While prepared, event withdraw produces active/swap_epoch instead of active/discard_proposal.
Peer configuration epoch activation controller: prepared / withdraw · case 04
While prepared, event withdraw produces active/swap_epoch instead of active/discard_proposal.
Peer configuration epoch activation controller: prepared / withdraw · case 05
While prepared, event withdraw produces active/swap_epoch instead of active/discard_proposal.
Peer configuration epoch activation controller: prepared / old epoch data · case 01
While prepared, event old_epoch_data produces prepared/process_new instead of prepared/process_old.
Peer configuration epoch activation controller: prepared / old epoch data · case 02
While prepared, event old_epoch_data produces prepared/process_new instead of prepared/process_old.
Peer configuration epoch activation controller: prepared / old epoch data · case 03
While prepared, event old_epoch_data produces prepared/process_new instead of prepared/process_old.
Peer configuration epoch activation controller: prepared / old epoch data · case 04
While prepared, event old_epoch_data produces prepared/process_new instead of prepared/process_old.
Peer configuration epoch activation controller: prepared / old epoch data · case 05
While prepared, event old_epoch_data produces prepared/process_new instead of prepared/process_old.
Peer configuration epoch activation controller: active / future epoch data · case 01
While active, event future_epoch_data produces active/process_new instead of active/reject_future.
Peer configuration epoch activation controller: active / future epoch data · case 02
While active, event future_epoch_data produces active/process_new instead of active/reject_future.
Peer configuration epoch activation controller: active / future epoch data · case 03
While active, event future_epoch_data produces active/process_new instead of active/reject_future.
Peer configuration epoch activation controller: active / future epoch data · case 04
While active, event future_epoch_data produces active/process_new instead of active/reject_future.
Peer configuration epoch activation controller: active / future epoch data · case 05
While active, event future_epoch_data produces active/process_new instead of active/reject_future.
Peer configuration epoch activation controller: pending / second proposal · case 01
While pending, event second_proposal produces pending/replace_staged instead of pending/reject_busy.
Peer configuration epoch activation controller: pending / second proposal · case 02
While pending, event second_proposal produces pending/replace_staged instead of pending/reject_busy.
Peer configuration epoch activation controller: pending / second proposal · case 03
While pending, event second_proposal produces pending/replace_staged instead of pending/reject_busy.
Peer configuration epoch activation controller: pending / second proposal · case 04
While pending, event second_proposal produces pending/replace_staged instead of pending/reject_busy.
Peer configuration epoch activation controller: pending / second proposal · case 05
While pending, event second_proposal produces pending/replace_staged instead of pending/reject_busy.
Peer configuration epoch activation controller: active / duplicate activation · case 01
While active, event duplicate_activation produces active/swap_again instead of active/ack_current.
Peer configuration epoch activation controller: active / duplicate activation · case 02
While active, event duplicate_activation produces active/swap_again instead of active/ack_current.
Peer configuration epoch activation controller: active / duplicate activation · case 03
While active, event duplicate_activation produces active/swap_again instead of active/ack_current.
Peer configuration epoch activation controller: active / duplicate activation · case 04
While active, event duplicate_activation produces active/swap_again instead of active/ack_current.
Peer configuration epoch activation controller: active / duplicate activation · case 05
While active, event duplicate_activation produces active/swap_again instead of active/ack_current.
Peer configuration epoch activation controller: prepared / restart · case 01
While prepared, event restart produces active/discard_proposal instead of recovering/load_prepared.
Peer configuration epoch activation controller: prepared / restart · case 02
While prepared, event restart produces active/discard_proposal instead of recovering/load_prepared.
Peer configuration epoch activation controller: prepared / restart · case 03
While prepared, event restart produces active/discard_proposal instead of recovering/load_prepared.
Peer configuration epoch activation controller: prepared / restart · case 04
While prepared, event restart produces active/discard_proposal instead of recovering/load_prepared.
Peer configuration epoch activation controller: prepared / restart · case 05
While prepared, event restart produces active/discard_proposal instead of recovering/load_prepared.
Application stream endpoint migration controller: home / move offer · case 01
While home, event move_offer produces away/switch_target instead of probing/probe_target.
Application stream endpoint migration controller: home / move offer · case 02
While home, event move_offer produces away/switch_target instead of probing/probe_target.
Application stream endpoint migration controller: home / move offer · case 03
While home, event move_offer produces away/switch_target instead of probing/probe_target.
Application stream endpoint migration controller: home / move offer · case 04
While home, event move_offer produces away/switch_target instead of probing/probe_target.
Application stream endpoint migration controller: home / move offer · case 05
While home, event move_offer produces away/switch_target instead of probing/probe_target.
Application stream endpoint migration controller: probing / target ready · case 01
While probing, event target_ready produces away/switch_target instead of draining/freeze_home_sequence.
Application stream endpoint migration controller: probing / target ready · case 02
While probing, event target_ready produces away/switch_target instead of draining/freeze_home_sequence.
Application stream endpoint migration controller: probing / target ready · case 03
While probing, event target_ready produces away/switch_target instead of draining/freeze_home_sequence.
Application stream endpoint migration controller: probing / target ready · case 04
While probing, event target_ready produces away/switch_target instead of draining/freeze_home_sequence.
Application stream endpoint migration controller: probing / target ready · case 05
While probing, event target_ready produces away/switch_target instead of draining/freeze_home_sequence.
Application stream endpoint migration controller: probing / target rejected · case 01
While probing, event target_rejected produces away/switch_target instead of home/discard_target.
Application stream endpoint migration controller: probing / target rejected · case 02
While probing, event target_rejected produces away/switch_target instead of home/discard_target.
Application stream endpoint migration controller: probing / target rejected · case 03
While probing, event target_rejected produces away/switch_target instead of home/discard_target.
Application stream endpoint migration controller: probing / target rejected · case 04
While probing, event target_rejected produces away/switch_target instead of home/discard_target.
Application stream endpoint migration controller: probing / target rejected · case 05
While probing, event target_rejected produces away/switch_target instead of home/discard_target.
Application stream endpoint migration controller: draining / home flushed · case 01
While draining, event home_flushed produces away/switch_target instead of switching/send_boundary.
Application stream endpoint migration controller: draining / home flushed · case 02
While draining, event home_flushed produces away/switch_target instead of switching/send_boundary.
Application stream endpoint migration controller: draining / home flushed · case 03
While draining, event home_flushed produces away/switch_target instead of switching/send_boundary.
Application stream endpoint migration controller: draining / home flushed · case 04
While draining, event home_flushed produces away/switch_target instead of switching/send_boundary.
Application stream endpoint migration controller: draining / home flushed · case 05
While draining, event home_flushed produces away/switch_target instead of switching/send_boundary.
Application stream endpoint migration controller: switching / boundary ack · case 01
While switching, event boundary_ack produces home/resume_home instead of away/switch_target.
Application stream endpoint migration controller: switching / boundary ack · case 02
While switching, event boundary_ack produces home/resume_home instead of away/switch_target.
Application stream endpoint migration controller: switching / boundary ack · case 03
While switching, event boundary_ack produces home/resume_home instead of away/switch_target.
Application stream endpoint migration controller: switching / boundary ack · case 04
While switching, event boundary_ack produces home/resume_home instead of away/switch_target.
Application stream endpoint migration controller: switching / boundary ack · case 05
While switching, event boundary_ack produces home/resume_home instead of away/switch_target.
Application stream endpoint migration controller: switching / old endpoint data · case 01
While switching, event old_endpoint_data produces switching/drop_all instead of switching/accept_before_boundary.
Application stream endpoint migration controller: switching / old endpoint data · case 02
While switching, event old_endpoint_data produces switching/drop_all instead of switching/accept_before_boundary.
Application stream endpoint migration controller: switching / old endpoint data · case 03
While switching, event old_endpoint_data produces switching/drop_all instead of switching/accept_before_boundary.
Application stream endpoint migration controller: switching / old endpoint data · case 04
While switching, event old_endpoint_data produces switching/drop_all instead of switching/accept_before_boundary.
Application stream endpoint migration controller: switching / old endpoint data · case 05
While switching, event old_endpoint_data produces switching/drop_all instead of switching/accept_before_boundary.
Application stream endpoint migration controller: away / old endpoint data · case 01
While away, event old_endpoint_data produces away/deliver instead of away/reject_old_endpoint.
Application stream endpoint migration controller: away / old endpoint data · case 02
While away, event old_endpoint_data produces away/deliver instead of away/reject_old_endpoint.
Application stream endpoint migration controller: away / old endpoint data · case 03
While away, event old_endpoint_data produces away/deliver instead of away/reject_old_endpoint.
Application stream endpoint migration controller: away / old endpoint data · case 04
While away, event old_endpoint_data produces away/deliver instead of away/reject_old_endpoint.
Application stream endpoint migration controller: away / old endpoint data · case 05
While away, event old_endpoint_data produces away/deliver instead of away/reject_old_endpoint.
Application stream endpoint migration controller: away / target lost · case 01
While away, event target_lost produces home/resume_home instead of suspended/report_unavailable.
Application stream endpoint migration controller: away / target lost · case 02
While away, event target_lost produces home/resume_home instead of suspended/report_unavailable.
Application stream endpoint migration controller: away / target lost · case 03
While away, event target_lost produces home/resume_home instead of suspended/report_unavailable.
Application stream endpoint migration controller: away / target lost · case 04
While away, event target_lost produces home/resume_home instead of suspended/report_unavailable.
Application stream endpoint migration controller: away / target lost · case 05
While away, event target_lost produces home/resume_home instead of suspended/report_unavailable.
Application stream endpoint migration controller: home / unsolicited boundary ack · case 01
While home, event unsolicited_boundary_ack produces away/switch_target instead of home/reject_unoffered.
Application stream endpoint migration controller: home / unsolicited boundary ack · case 02
While home, event unsolicited_boundary_ack produces away/switch_target instead of home/reject_unoffered.
Application stream endpoint migration controller: home / unsolicited boundary ack · case 03
While home, event unsolicited_boundary_ack produces away/switch_target instead of home/reject_unoffered.
Application stream endpoint migration controller: home / unsolicited boundary ack · case 04
While home, event unsolicited_boundary_ack produces away/switch_target instead of home/reject_unoffered.
Application stream endpoint migration controller: home / unsolicited boundary ack · case 05
While home, event unsolicited_boundary_ack produces away/switch_target instead of home/reject_unoffered.
Application stream endpoint migration controller: draining / new application data · case 01
While draining, event new_application_data produces draining/send_home instead of draining/queue_after_boundary.
Application stream endpoint migration controller: draining / new application data · case 02
While draining, event new_application_data produces draining/send_home instead of draining/queue_after_boundary.
Application stream endpoint migration controller: draining / new application data · case 03
While draining, event new_application_data produces draining/send_home instead of draining/queue_after_boundary.
Application stream endpoint migration controller: draining / new application data · case 04
While draining, event new_application_data produces draining/send_home instead of draining/queue_after_boundary.
Application stream endpoint migration controller: draining / new application data · case 05
While draining, event new_application_data produces draining/send_home instead of draining/queue_after_boundary.
Scoped address assignment controller: unassigned / solicit · case 01
While unassigned, event solicit produces bound/use_default instead of discovering/send_discovery.
Scoped address assignment controller: unassigned / solicit · case 02
While unassigned, event solicit produces bound/use_default instead of discovering/send_discovery.
Scoped address assignment controller: unassigned / solicit · case 03
While unassigned, event solicit produces bound/use_default instead of discovering/send_discovery.
Scoped address assignment controller: unassigned / solicit · case 04
While unassigned, event solicit produces bound/use_default instead of discovering/send_discovery.
Scoped address assignment controller: unassigned / solicit · case 05
While unassigned, event solicit produces bound/use_default instead of discovering/send_discovery.
Scoped address assignment controller: discovering / offer · case 01
While discovering, event offer produces bound/use_address instead of offered/record_offer.
Scoped address assignment controller: discovering / offer · case 02
While discovering, event offer produces bound/use_address instead of offered/record_offer.
Scoped address assignment controller: discovering / offer · case 03
While discovering, event offer produces bound/use_address instead of offered/record_offer.
Scoped address assignment controller: discovering / offer · case 04
While discovering, event offer produces bound/use_address instead of offered/record_offer.
Scoped address assignment controller: discovering / offer · case 05
While discovering, event offer produces bound/use_address instead of offered/record_offer.
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 ↗