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
Retry reconciliation with a server receipt: An in-progress operation is duplicated or rejected as a content conflict · case 01
An in-progress operation is duplicated or rejected as a content conflict
Retry reconciliation with a server receipt: An in-progress operation is duplicated or rejected as a content conflict · case 02
An in-progress operation is duplicated or rejected as a content conflict
Retry reconciliation with a server receipt: An in-progress operation is duplicated or rejected as a content conflict · case 03
An in-progress operation is duplicated or rejected as a content conflict
Retry reconciliation with a server receipt: An in-progress operation is duplicated or rejected as a content conflict · case 04
An in-progress operation is duplicated or rejected as a content conflict
Retry reconciliation with a server receipt: An in-progress operation is duplicated or rejected as a content conflict · case 05
An in-progress operation is duplicated or rejected as a content conflict
Retry reconciliation with a server receipt: A committed retry returns request data instead of saved response · case 01
A committed retry returns request data instead of saved response
Retry reconciliation with a server receipt: A committed retry returns request data instead of saved response · case 02
A committed retry returns request data instead of saved response
Retry reconciliation with a server receipt: A committed retry returns request data instead of saved response · case 03
A committed retry returns request data instead of saved response
Retry reconciliation with a server receipt: A committed retry returns request data instead of saved response · case 04
A committed retry returns request data instead of saved response
Retry reconciliation with a server receipt: A committed retry returns request data instead of saved response · case 05
A committed retry returns request data instead of saved response
Retry reconciliation with a server receipt: Late duplicate commits overwrite the first durable result · case 01
Late duplicate commits overwrite the first durable result
Retry reconciliation with a server receipt: Late duplicate commits overwrite the first durable result · case 02
Late duplicate commits overwrite the first durable result
Retry reconciliation with a server receipt: Late duplicate commits overwrite the first durable result · case 03
Late duplicate commits overwrite the first durable result
Retry reconciliation with a server receipt: Late duplicate commits overwrite the first durable result · case 04
Late duplicate commits overwrite the first durable result
Retry reconciliation with a server receipt: Late duplicate commits overwrite the first durable result · case 05
Late duplicate commits overwrite the first durable result
Retry reconciliation with a server receipt: A durable commit remains reported as an in-flight request · case 01
A durable commit remains reported as an in-flight request
Retry reconciliation with a server receipt: A durable commit remains reported as an in-flight request · case 02
A durable commit remains reported as an in-flight request
Retry reconciliation with a server receipt: A durable commit remains reported as an in-flight request · case 03
A durable commit remains reported as an in-flight request
Retry reconciliation with a server receipt: A durable commit remains reported as an in-flight request · case 04
A durable commit remains reported as an in-flight request
Retry reconciliation with a server receipt: A durable commit remains reported as an in-flight request · case 05
A durable commit remains reported as an in-flight request
Retry reconciliation with a server receipt: Commit stores the operation key instead of its response payload · case 01
Commit stores the operation key instead of its response payload
Retry reconciliation with a server receipt: Commit stores the operation key instead of its response payload · case 02
Commit stores the operation key instead of its response payload
Retry reconciliation with a server receipt: Commit stores the operation key instead of its response payload · case 03
Commit stores the operation key instead of its response payload
Retry reconciliation with a server receipt: Commit stores the operation key instead of its response payload · case 04
Commit stores the operation key instead of its response payload
Retry reconciliation with a server receipt: Commit stores the operation key instead of its response payload · case 05
Commit stores the operation key instead of its response payload
Retry reconciliation with a server receipt: Receipt eviction removes other requests or leaves the target replayable · case 01
Receipt eviction removes other requests or leaves the target replayable
Retry reconciliation with a server receipt: Receipt eviction removes other requests or leaves the target replayable · case 02
Receipt eviction removes other requests or leaves the target replayable
Retry reconciliation with a server receipt: Receipt eviction removes other requests or leaves the target replayable · case 03
Receipt eviction removes other requests or leaves the target replayable
Retry reconciliation with a server receipt: Receipt eviction removes other requests or leaves the target replayable · case 04
Receipt eviction removes other requests or leaves the target replayable
Retry reconciliation with a server receipt: Receipt eviction removes other requests or leaves the target replayable · case 05
Receipt eviction removes other requests or leaves the target replayable
Retry only unresolved batch members: Retry batch reorders or deduplicates requested positions · case 01
Retry batch reorders or deduplicates requested positions
Retry only unresolved batch members: Retry batch reorders or deduplicates requested positions · case 02
Retry batch reorders or deduplicates requested positions
Retry only unresolved batch members: Retry batch reorders or deduplicates requested positions · case 03
Retry batch reorders or deduplicates requested positions
Retry only unresolved batch members: Retry batch reorders or deduplicates requested positions · case 04
Retry batch reorders or deduplicates requested positions
Retry only unresolved batch members: Retry batch reorders or deduplicates requested positions · case 05
Retry batch reorders or deduplicates requested positions
Retry only unresolved batch members: A fresh batch inherits completed results from an earlier operation · case 01
A fresh batch inherits completed results from an earlier operation
Retry only unresolved batch members: A fresh batch inherits completed results from an earlier operation · case 02
A fresh batch inherits completed results from an earlier operation
Retry only unresolved batch members: A fresh batch inherits completed results from an earlier operation · case 03
A fresh batch inherits completed results from an earlier operation
Retry only unresolved batch members: A fresh batch inherits completed results from an earlier operation · case 04
A fresh batch inherits completed results from an earlier operation
Retry only unresolved batch members: A fresh batch inherits completed results from an earlier operation · case 05
A fresh batch inherits completed results from an earlier operation
Retry only unresolved batch members: An unsolicited result injects an item into the next retry batch · case 01
An unsolicited result injects an item into the next retry batch
Retry only unresolved batch members: An unsolicited result injects an item into the next retry batch · case 02
An unsolicited result injects an item into the next retry batch
Retry only unresolved batch members: An unsolicited result injects an item into the next retry batch · case 03
An unsolicited result injects an item into the next retry batch
Retry only unresolved batch members: An unsolicited result injects an item into the next retry batch · case 04
An unsolicited result injects an item into the next retry batch
Retry only unresolved batch members: An unsolicited result injects an item into the next retry batch · case 05
An unsolicited result injects an item into the next retry batch
Retry only unresolved batch members: Late failures overwrite a successful batch member · case 01
Late failures overwrite a successful batch member
Retry only unresolved batch members: Late failures overwrite a successful batch member · case 02
Late failures overwrite a successful batch member
Retry only unresolved batch members: Late failures overwrite a successful batch member · case 03
Late failures overwrite a successful batch member
Retry only unresolved batch members: Late failures overwrite a successful batch member · case 04
Late failures overwrite a successful batch member
Retry only unresolved batch members: Late failures overwrite a successful batch member · case 05
Late failures overwrite a successful batch member
Retry only unresolved batch members: A permanently rejected member reenters the retry set · case 01
A permanently rejected member reenters the retry set
Retry only unresolved batch members: A permanently rejected member reenters the retry set · case 02
A permanently rejected member reenters the retry set
Retry only unresolved batch members: A permanently rejected member reenters the retry set · case 03
A permanently rejected member reenters the retry set
Retry only unresolved batch members: A permanently rejected member reenters the retry set · case 04
A permanently rejected member reenters the retry set
Retry only unresolved batch members: A permanently rejected member reenters the retry set · case 05
A permanently rejected member reenters the retry set
Retry only unresolved batch members: Successful batch retry loses the returned value · case 01
Successful batch retry loses the returned value
Retry only unresolved batch members: Successful batch retry loses the returned value · case 02
Successful batch retry loses the returned value
Retry only unresolved batch members: Successful batch retry loses the returned value · case 03
Successful batch retry loses the returned value
Retry only unresolved batch members: Successful batch retry loses the returned value · case 04
Successful batch retry loses the returned value
Retry only unresolved batch members: Successful batch retry loses the returned value · case 05
Successful batch retry loses the returned value
Retry only unresolved batch members: Permanent failures are resent in a partial retry · case 01
Permanent failures are resent in a partial retry
Retry only unresolved batch members: Permanent failures are resent in a partial retry · case 02
Permanent failures are resent in a partial retry
Retry only unresolved batch members: Permanent failures are resent in a partial retry · case 03
Permanent failures are resent in a partial retry
Retry only unresolved batch members: Permanent failures are resent in a partial retry · case 04
Permanent failures are resent in a partial retry
Retry only unresolved batch members: Permanent failures are resent in a partial retry · case 05
Permanent failures are resent in a partial retry
Retry only unresolved batch members: Retryable batch failure is prematurely finalized · case 01
Retryable batch failure is prematurely finalized
Retry only unresolved batch members: Retryable batch failure is prematurely finalized · case 02
Retryable batch failure is prematurely finalized
Retry only unresolved batch members: Retryable batch failure is prematurely finalized · case 03
Retryable batch failure is prematurely finalized
Retry only unresolved batch members: Retryable batch failure is prematurely finalized · case 04
Retryable batch failure is prematurely finalized
Retry only unresolved batch members: Retryable batch failure is prematurely finalized · case 05
Retryable batch failure is prematurely finalized
Retry only unresolved batch members: Partial retry drops pending or explicitly retryable members · case 01
Partial retry drops pending or explicitly retryable members
Retry only unresolved batch members: Partial retry drops pending or explicitly retryable members · case 02
Partial retry drops pending or explicitly retryable members
Retry only unresolved batch members: Partial retry drops pending or explicitly retryable members · case 03
Partial retry drops pending or explicitly retryable members
Retry only unresolved batch members: Partial retry drops pending or explicitly retryable members · case 04
Partial retry drops pending or explicitly retryable members
Retry only unresolved batch members: Partial retry drops pending or explicitly retryable members · case 05
Partial retry drops pending or explicitly retryable members
Retry only unresolved batch members: Final batch response loses original position mapping · case 01
Final batch response loses original position mapping
Retry only unresolved batch members: Final batch response loses original position mapping · case 02
Final batch response loses original position mapping
Retry only unresolved batch members: Final batch response loses original position mapping · case 03
Final batch response loses original position mapping
Retry only unresolved batch members: Final batch response loses original position mapping · case 04
Final batch response loses original position mapping
Retry only unresolved batch members: Final batch response loses original position mapping · case 05
Final batch response loses original position mapping
Retry after consumer-visible response delivery: Retry starts after an empty response already completed · case 01
Retry starts after an empty response already completed
Retry after consumer-visible response delivery: Retry starts after an empty response already completed · case 02
Retry starts after an empty response already completed
Retry after consumer-visible response delivery: Retry starts after an empty response already completed · case 03
Retry starts after an empty response already completed
Retry after consumer-visible response delivery: Retry starts after an empty response already completed · case 04
Retry starts after an empty response already completed
Retry after consumer-visible response delivery: Retry starts after an empty response already completed · case 05
Retry starts after an empty response already completed
Retry after consumer-visible response delivery: An initial response attempt is not marked active · case 01
An initial response attempt is not marked active
Retry after consumer-visible response delivery: An initial response attempt is not marked active · case 02
An initial response attempt is not marked active
Retry after consumer-visible response delivery: An initial response attempt is not marked active · case 03
An initial response attempt is not marked active
Retry after consumer-visible response delivery: An initial response attempt is not marked active · case 04
An initial response attempt is not marked active
Retry after consumer-visible response delivery: An initial response attempt is not marked active · case 05
An initial response attempt is not marked active
Retry after consumer-visible response delivery: A retry transport failure inherits the preceding response status · case 01
A retry transport failure inherits the preceding response status
Retry after consumer-visible response delivery: A retry transport failure inherits the preceding response status · case 02
A retry transport failure inherits the preceding response status
Retry after consumer-visible response delivery: A retry transport failure inherits the preceding response status · case 03
A retry transport failure inherits the preceding response status
Retry after consumer-visible response delivery: A retry transport failure inherits the preceding response status · case 04
A retry transport failure inherits the preceding response status
Retry after consumer-visible response delivery: A retry transport failure inherits the preceding response status · case 05
A retry transport failure inherits the preceding response status
Retry after consumer-visible response delivery: Partial response errors lose the actual HTTP response status · case 01
Partial response errors lose the actual HTTP response status
Retry after consumer-visible response delivery: Partial response errors lose the actual HTTP response status · case 02
Partial response errors lose the actual HTTP response status
Retry after consumer-visible response delivery: Partial response errors lose the actual HTTP response status · case 03
Partial response errors lose the actual HTTP response status
Retry after consumer-visible response delivery: Partial response errors lose the actual HTTP response status · case 04
Partial response errors lose the actual HTTP response status
Retry after consumer-visible response delivery: Partial response errors lose the actual HTTP response status · case 05
Partial response errors lose the actual HTTP response status
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 ↗