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
Purge messages through a selected boundary: A moving purge boundary consumes messages published after purge began · case 01
The queue purge operation is admitted even though a moving purge boundary consumes messages published after purge began.
Purge messages through a selected boundary: A moving purge boundary consumes messages published after purge began · case 02
The queue purge operation is admitted even though a moving purge boundary consumes messages published after purge began.
Purge messages through a selected boundary: A moving purge boundary consumes messages published after purge began · case 03
The queue purge operation is admitted even though a moving purge boundary consumes messages published after purge began.
Purge messages through a selected boundary: A moving purge boundary consumes messages published after purge began · case 04
The queue purge operation is admitted even though a moving purge boundary consumes messages published after purge began.
Purge messages through a selected boundary: A moving purge boundary consumes messages published after purge began · case 05
The queue purge operation is admitted even though a moving purge boundary consumes messages published after purge began.
Purge messages through a selected boundary: Purge deletes an actively reserved delivery · case 01
The queue purge operation is admitted even though purge deletes an actively reserved delivery.
Purge messages through a selected boundary: Purge deletes an actively reserved delivery · case 02
The queue purge operation is admitted even though purge deletes an actively reserved delivery.
Purge messages through a selected boundary: Purge deletes an actively reserved delivery · case 03
The queue purge operation is admitted even though purge deletes an actively reserved delivery.
Purge messages through a selected boundary: Purge deletes an actively reserved delivery · case 04
The queue purge operation is admitted even though purge deletes an actively reserved delivery.
Purge messages through a selected boundary: Purge deletes an actively reserved delivery · case 05
The queue purge operation is admitted even though purge deletes an actively reserved delivery.
Purge messages through a selected boundary: Purge crosses into another tenant queue · case 01
The queue purge operation is admitted even though purge crosses into another tenant queue.
Purge messages through a selected boundary: Purge crosses into another tenant queue · case 02
The queue purge operation is admitted even though purge crosses into another tenant queue.
Purge messages through a selected boundary: Purge crosses into another tenant queue · case 03
The queue purge operation is admitted even though purge crosses into another tenant queue.
Purge messages through a selected boundary: Purge crosses into another tenant queue · case 04
The queue purge operation is admitted even though purge crosses into another tenant queue.
Purge messages through a selected boundary: Purge crosses into another tenant queue · case 05
The queue purge operation is admitted even though purge crosses into another tenant queue.
Purge messages through a selected boundary: A delayed purge targets a recreated queue with the same name · case 01
The queue purge operation is admitted even though a delayed purge targets a recreated queue with the same name.
Purge messages through a selected boundary: A delayed purge targets a recreated queue with the same name · case 02
The queue purge operation is admitted even though a delayed purge targets a recreated queue with the same name.
Purge messages through a selected boundary: A delayed purge targets a recreated queue with the same name · case 03
The queue purge operation is admitted even though a delayed purge targets a recreated queue with the same name.
Purge messages through a selected boundary: A delayed purge targets a recreated queue with the same name · case 04
The queue purge operation is admitted even though a delayed purge targets a recreated queue with the same name.
Purge messages through a selected boundary: A delayed purge targets a recreated queue with the same name · case 05
The queue purge operation is admitted even though a delayed purge targets a recreated queue with the same name.
Purge messages through a selected boundary: Purge ignores an explicit retention hold · case 01
The queue purge operation is admitted even though purge ignores an explicit retention hold.
Purge messages through a selected boundary: Purge ignores an explicit retention hold · case 02
The queue purge operation is admitted even though purge ignores an explicit retention hold.
Purge messages through a selected boundary: Purge ignores an explicit retention hold · case 03
The queue purge operation is admitted even though purge ignores an explicit retention hold.
Purge messages through a selected boundary: Purge ignores an explicit retention hold · case 04
The queue purge operation is admitted even though purge ignores an explicit retention hold.
Purge messages through a selected boundary: Purge ignores an explicit retention hold · case 05
The queue purge operation is admitted even though purge ignores an explicit retention hold.
Admit a remote operation retry: A permanent rejection triggers another attempt · case 01
The retry admission operation is admitted even though a permanent rejection triggers another attempt.
Admit a remote operation retry: A permanent rejection triggers another attempt · case 02
The retry admission operation is admitted even though a permanent rejection triggers another attempt.
Admit a remote operation retry: A permanent rejection triggers another attempt · case 03
The retry admission operation is admitted even though a permanent rejection triggers another attempt.
Admit a remote operation retry: A permanent rejection triggers another attempt · case 04
The retry admission operation is admitted even though a permanent rejection triggers another attempt.
Admit a remote operation retry: A permanent rejection triggers another attempt · case 05
The retry admission operation is admitted even though a permanent rejection triggers another attempt.
Admit a remote operation retry: An exhausted attempt budget permits one more request · case 01
The retry admission operation is admitted even though an exhausted attempt budget permits one more request.
Admit a remote operation retry: An exhausted attempt budget permits one more request · case 02
The retry admission operation is admitted even though an exhausted attempt budget permits one more request.
Admit a remote operation retry: An exhausted attempt budget permits one more request · case 03
The retry admission operation is admitted even though an exhausted attempt budget permits one more request.
Admit a remote operation retry: An exhausted attempt budget permits one more request · case 04
The retry admission operation is admitted even though an exhausted attempt budget permits one more request.
Admit a remote operation retry: An exhausted attempt budget permits one more request · case 05
The retry admission operation is admitted even though an exhausted attempt budget permits one more request.
Admit a remote operation retry: A retry cannot finish within its remaining request deadline · case 01
The retry admission operation is admitted even though a retry cannot finish within its remaining request deadline.
Admit a remote operation retry: A retry cannot finish within its remaining request deadline · case 02
The retry admission operation is admitted even though a retry cannot finish within its remaining request deadline.
Admit a remote operation retry: A retry cannot finish within its remaining request deadline · case 03
The retry admission operation is admitted even though a retry cannot finish within its remaining request deadline.
Admit a remote operation retry: A retry cannot finish within its remaining request deadline · case 04
The retry admission operation is admitted even though a retry cannot finish within its remaining request deadline.
Admit a remote operation retry: A retry cannot finish within its remaining request deadline · case 05
The retry admission operation is admitted even though a retry cannot finish within its remaining request deadline.
Admit a remote operation retry: A non-idempotent write is retried without an identity key · case 01
The retry admission operation is admitted even though a non-idempotent write is retried without an identity key.
Admit a remote operation retry: A non-idempotent write is retried without an identity key · case 02
The retry admission operation is admitted even though a non-idempotent write is retried without an identity key.
Admit a remote operation retry: A non-idempotent write is retried without an identity key · case 03
The retry admission operation is admitted even though a non-idempotent write is retried without an identity key.
Admit a remote operation retry: A non-idempotent write is retried without an identity key · case 04
The retry admission operation is admitted even though a non-idempotent write is retried without an identity key.
Admit a remote operation retry: A non-idempotent write is retried without an identity key · case 05
The retry admission operation is admitted even though a non-idempotent write is retried without an identity key.
Admit a remote operation retry: A retry ignores the server requested wait period · case 01
The retry admission operation is admitted even though a retry ignores the server requested wait period.
Admit a remote operation retry: A retry ignores the server requested wait period · case 02
The retry admission operation is admitted even though a retry ignores the server requested wait period.
Admit a remote operation retry: A retry ignores the server requested wait period · case 03
The retry admission operation is admitted even though a retry ignores the server requested wait period.
Admit a remote operation retry: A retry ignores the server requested wait period · case 04
The retry admission operation is admitted even though a retry ignores the server requested wait period.
Admit a remote operation retry: A retry ignores the server requested wait period · case 05
The retry admission operation is admitted even though a retry ignores the server requested wait period.
Allow a half-open circuit probe: A probe runs before the open-state cooldown elapses · case 01
The circuit probe operation is admitted even though a probe runs before the open-state cooldown elapses.
Allow a half-open circuit probe: A probe runs before the open-state cooldown elapses · case 02
The circuit probe operation is admitted even though a probe runs before the open-state cooldown elapses.
Allow a half-open circuit probe: A probe runs before the open-state cooldown elapses · case 03
The circuit probe operation is admitted even though a probe runs before the open-state cooldown elapses.
Allow a half-open circuit probe: A probe runs before the open-state cooldown elapses · case 04
The circuit probe operation is admitted even though a probe runs before the open-state cooldown elapses.
Allow a half-open circuit probe: A probe runs before the open-state cooldown elapses · case 05
The circuit probe operation is admitted even though a probe runs before the open-state cooldown elapses.
Allow a half-open circuit probe: Concurrent requests occupy the single half-open probe slot · case 01
The circuit probe operation is admitted even though concurrent requests occupy the single half-open probe slot.
Allow a half-open circuit probe: Concurrent requests occupy the single half-open probe slot · case 02
The circuit probe operation is admitted even though concurrent requests occupy the single half-open probe slot.
Allow a half-open circuit probe: Concurrent requests occupy the single half-open probe slot · case 03
The circuit probe operation is admitted even though concurrent requests occupy the single half-open probe slot.
Allow a half-open circuit probe: Concurrent requests occupy the single half-open probe slot · case 04
The circuit probe operation is admitted even though concurrent requests occupy the single half-open probe slot.
Allow a half-open circuit probe: Concurrent requests occupy the single half-open probe slot · case 05
The circuit probe operation is admitted even though concurrent requests occupy the single half-open probe slot.
Allow a half-open circuit probe: A stale timer probes a newly opened circuit generation · case 01
The circuit probe operation is admitted even though a stale timer probes a newly opened circuit generation.
Allow a half-open circuit probe: A stale timer probes a newly opened circuit generation · case 02
The circuit probe operation is admitted even though a stale timer probes a newly opened circuit generation.
Allow a half-open circuit probe: A stale timer probes a newly opened circuit generation · case 03
The circuit probe operation is admitted even though a stale timer probes a newly opened circuit generation.
Allow a half-open circuit probe: A stale timer probes a newly opened circuit generation · case 04
The circuit probe operation is admitted even though a stale timer probes a newly opened circuit generation.
Allow a half-open circuit probe: A stale timer probes a newly opened circuit generation · case 05
The circuit probe operation is admitted even though a stale timer probes a newly opened circuit generation.
Allow a half-open circuit probe: A probe targets an endpoint removed from service discovery · case 01
The circuit probe operation is admitted even though a probe targets an endpoint removed from service discovery.
Allow a half-open circuit probe: A probe targets an endpoint removed from service discovery · case 02
The circuit probe operation is admitted even though a probe targets an endpoint removed from service discovery.
Allow a half-open circuit probe: A probe targets an endpoint removed from service discovery · case 03
The circuit probe operation is admitted even though a probe targets an endpoint removed from service discovery.
Allow a half-open circuit probe: A probe targets an endpoint removed from service discovery · case 04
The circuit probe operation is admitted even though a probe targets an endpoint removed from service discovery.
Allow a half-open circuit probe: A probe targets an endpoint removed from service discovery · case 05
The circuit probe operation is admitted even though a probe targets an endpoint removed from service discovery.
Allow a half-open circuit probe: A probe is started for an already expired caller · case 01
The circuit probe operation is admitted even though a probe is started for an already expired caller.
Allow a half-open circuit probe: A probe is started for an already expired caller · case 02
The circuit probe operation is admitted even though a probe is started for an already expired caller.
Allow a half-open circuit probe: A probe is started for an already expired caller · case 03
The circuit probe operation is admitted even though a probe is started for an already expired caller.
Allow a half-open circuit probe: A probe is started for an already expired caller · case 04
The circuit probe operation is admitted even though a probe is started for an already expired caller.
Allow a half-open circuit probe: A probe is started for an already expired caller · case 05
The circuit probe operation is admitted even though a probe is started for an already expired caller.
Launch a speculative hedged request: A duplicate request is launched before the hedge delay · case 01
The hedge request operation is admitted even though a duplicate request is launched before the hedge delay.
Launch a speculative hedged request: A duplicate request is launched before the hedge delay · case 02
The hedge request operation is admitted even though a duplicate request is launched before the hedge delay.
Launch a speculative hedged request: A duplicate request is launched before the hedge delay · case 03
The hedge request operation is admitted even though a duplicate request is launched before the hedge delay.
Launch a speculative hedged request: A duplicate request is launched before the hedge delay · case 04
The hedge request operation is admitted even though a duplicate request is launched before the hedge delay.
Launch a speculative hedged request: A duplicate request is launched before the hedge delay · case 05
The hedge request operation is admitted even though a duplicate request is launched before the hedge delay.
Launch a speculative hedged request: A hedge starts after the primary already completed · case 01
The hedge request operation is admitted even though a hedge starts after the primary already completed.
Launch a speculative hedged request: A hedge starts after the primary already completed · case 02
The hedge request operation is admitted even though a hedge starts after the primary already completed.
Launch a speculative hedged request: A hedge starts after the primary already completed · case 03
The hedge request operation is admitted even though a hedge starts after the primary already completed.
Launch a speculative hedged request: A hedge starts after the primary already completed · case 04
The hedge request operation is admitted even though a hedge starts after the primary already completed.
Launch a speculative hedged request: A hedge starts after the primary already completed · case 05
The hedge request operation is admitted even though a hedge starts after the primary already completed.
Launch a speculative hedged request: Primary and hedge share the same correlated failure domain · case 01
The hedge request operation is admitted even though primary and hedge share the same correlated failure domain.
Launch a speculative hedged request: Primary and hedge share the same correlated failure domain · case 02
The hedge request operation is admitted even though primary and hedge share the same correlated failure domain.
Launch a speculative hedged request: Primary and hedge share the same correlated failure domain · case 03
The hedge request operation is admitted even though primary and hedge share the same correlated failure domain.
Launch a speculative hedged request: Primary and hedge share the same correlated failure domain · case 04
The hedge request operation is admitted even though primary and hedge share the same correlated failure domain.
Launch a speculative hedged request: Primary and hedge share the same correlated failure domain · case 05
The hedge request operation is admitted even though primary and hedge share the same correlated failure domain.
Launch a speculative hedged request: Speculation consumes more than the allowed duplicate capacity · case 01
The hedge request operation is admitted even though speculation consumes more than the allowed duplicate capacity.
Launch a speculative hedged request: Speculation consumes more than the allowed duplicate capacity · case 02
The hedge request operation is admitted even though speculation consumes more than the allowed duplicate capacity.
Launch a speculative hedged request: Speculation consumes more than the allowed duplicate capacity · case 03
The hedge request operation is admitted even though speculation consumes more than the allowed duplicate capacity.
Launch a speculative hedged request: Speculation consumes more than the allowed duplicate capacity · case 04
The hedge request operation is admitted even though speculation consumes more than the allowed duplicate capacity.
Launch a speculative hedged request: Speculation consumes more than the allowed duplicate capacity · case 05
The hedge request operation is admitted even though speculation consumes more than the allowed duplicate capacity.
Launch a speculative hedged request: A hedge duplicates a non-repeatable side effect · case 01
The hedge request operation is admitted even though a hedge duplicates a non-repeatable side effect.
Launch a speculative hedged request: A hedge duplicates a non-repeatable side effect · case 02
The hedge request operation is admitted even though a hedge duplicates a non-repeatable side effect.
Launch a speculative hedged request: A hedge duplicates a non-repeatable side effect · case 03
The hedge request operation is admitted even though a hedge duplicates a non-repeatable side effect.
Launch a speculative hedged request: A hedge duplicates a non-repeatable side effect · case 04
The hedge request operation is admitted even though a hedge duplicates a non-repeatable side effect.
Launch a speculative hedged request: A hedge duplicates a non-repeatable side effect · case 05
The hedge request operation is admitted even though a hedge duplicates a non-repeatable side effect.
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 ↗