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
Nested client retry ownership: Nested retry logic spends a child budget and amplifies attempts · case 01
Nested retry logic spends a child budget and amplifies attempts
Nested client retry ownership: Nested retry logic spends a child budget and amplifies attempts · case 02
Nested retry logic spends a child budget and amplifies attempts
Nested client retry ownership: Nested retry logic spends a child budget and amplifies attempts · case 03
Nested retry logic spends a child budget and amplifies attempts
Nested client retry ownership: Nested retry logic spends a child budget and amplifies attempts · case 04
Nested retry logic spends a child budget and amplifies attempts
Nested client retry ownership: Nested retry logic spends a child budget and amplifies attempts · case 05
Nested retry logic spends a child budget and amplifies attempts
Nested client retry ownership: Retry admission spends beyond the owning scope cap · case 01
Retry admission spends beyond the owning scope cap
Nested client retry ownership: Retry admission spends beyond the owning scope cap · case 02
Retry admission spends beyond the owning scope cap
Nested client retry ownership: Retry admission spends beyond the owning scope cap · case 03
Retry admission spends beyond the owning scope cap
Nested client retry ownership: Retry admission spends beyond the owning scope cap · case 04
Retry admission spends beyond the owning scope cap
Nested client retry ownership: Retry admission spends beyond the owning scope cap · case 05
Retry admission spends beyond the owning scope cap
Nested client retry ownership: A retry consumes the wrong number of parent budget slots · case 01
A retry consumes the wrong number of parent budget slots
Nested client retry ownership: A retry consumes the wrong number of parent budget slots · case 02
A retry consumes the wrong number of parent budget slots
Nested client retry ownership: A retry consumes the wrong number of parent budget slots · case 03
A retry consumes the wrong number of parent budget slots
Nested client retry ownership: A retry consumes the wrong number of parent budget slots · case 04
A retry consumes the wrong number of parent budget slots
Nested client retry ownership: A retry consumes the wrong number of parent budget slots · case 05
A retry consumes the wrong number of parent budget slots
Nested client retry ownership: Exhaustion is attributed to a child rather than the scope refusing work · case 01
Exhaustion is attributed to a child rather than the scope refusing work
Nested client retry ownership: Exhaustion is attributed to a child rather than the scope refusing work · case 02
Exhaustion is attributed to a child rather than the scope refusing work
Nested client retry ownership: Exhaustion is attributed to a child rather than the scope refusing work · case 03
Exhaustion is attributed to a child rather than the scope refusing work
Nested client retry ownership: Exhaustion is attributed to a child rather than the scope refusing work · case 04
Exhaustion is attributed to a child rather than the scope refusing work
Nested client retry ownership: Exhaustion is attributed to a child rather than the scope refusing work · case 05
Exhaustion is attributed to a child rather than the scope refusing work
Nested client retry ownership: Retry ownership metadata names the wrong layer · case 01
Retry ownership metadata names the wrong layer
Nested client retry ownership: Retry ownership metadata names the wrong layer · case 02
Retry ownership metadata names the wrong layer
Nested client retry ownership: Retry ownership metadata names the wrong layer · case 03
Retry ownership metadata names the wrong layer
Nested client retry ownership: Retry ownership metadata names the wrong layer · case 04
Retry ownership metadata names the wrong layer
Nested client retry ownership: Retry ownership metadata names the wrong layer · case 05
Retry ownership metadata names the wrong layer
Nested client retry ownership: A failure outside a retry scope is converted to an owned retry outcome · case 01
A failure outside a retry scope is converted to an owned retry outcome
Nested client retry ownership: A failure outside a retry scope is converted to an owned retry outcome · case 02
A failure outside a retry scope is converted to an owned retry outcome
Nested client retry ownership: A failure outside a retry scope is converted to an owned retry outcome · case 03
A failure outside a retry scope is converted to an owned retry outcome
Nested client retry ownership: A failure outside a retry scope is converted to an owned retry outcome · case 04
A failure outside a retry scope is converted to an owned retry outcome
Nested client retry ownership: A failure outside a retry scope is converted to an owned retry outcome · case 05
A failure outside a retry scope is converted to an owned retry outcome
Late response fencing between retry attempts: Retry attempt identifiers are reused or skip the caller-visible generation · case 01
Retry attempt identifiers are reused or skip the caller-visible generation
Late response fencing between retry attempts: Retry attempt identifiers are reused or skip the caller-visible generation · case 02
Retry attempt identifiers are reused or skip the caller-visible generation
Late response fencing between retry attempts: Retry attempt identifiers are reused or skip the caller-visible generation · case 03
Retry attempt identifiers are reused or skip the caller-visible generation
Late response fencing between retry attempts: Retry attempt identifiers are reused or skip the caller-visible generation · case 04
Retry attempt identifiers are reused or skip the caller-visible generation
Late response fencing between retry attempts: Retry attempt identifiers are reused or skip the caller-visible generation · case 05
Retry attempt identifiers are reused or skip the caller-visible generation
Late response fencing between retry attempts: Later retry attempts cannot receive their own response · case 01
Later retry attempts cannot receive their own response
Late response fencing between retry attempts: Later retry attempts cannot receive their own response · case 02
Later retry attempts cannot receive their own response
Late response fencing between retry attempts: Later retry attempts cannot receive their own response · case 03
Later retry attempts cannot receive their own response
Late response fencing between retry attempts: Later retry attempts cannot receive their own response · case 04
Later retry attempts cannot receive their own response
Late response fencing between retry attempts: Later retry attempts cannot receive their own response · case 05
Later retry attempts cannot receive their own response
Late response fencing between retry attempts: An old timeout invalidates a newer retry attempt · case 01
An old timeout invalidates a newer retry attempt
Late response fencing between retry attempts: An old timeout invalidates a newer retry attempt · case 02
An old timeout invalidates a newer retry attempt
Late response fencing between retry attempts: An old timeout invalidates a newer retry attempt · case 03
An old timeout invalidates a newer retry attempt
Late response fencing between retry attempts: An old timeout invalidates a newer retry attempt · case 04
An old timeout invalidates a newer retry attempt
Late response fencing between retry attempts: An old timeout invalidates a newer retry attempt · case 05
An old timeout invalidates a newer retry attempt
Late response fencing between retry attempts: Cancelling an active attempt does not stop future retries · case 01
Cancelling an active attempt does not stop future retries
Late response fencing between retry attempts: Cancelling an active attempt does not stop future retries · case 02
Cancelling an active attempt does not stop future retries
Late response fencing between retry attempts: Cancelling an active attempt does not stop future retries · case 03
Cancelling an active attempt does not stop future retries
Late response fencing between retry attempts: Cancelling an active attempt does not stop future retries · case 04
Cancelling an active attempt does not stop future retries
Late response fencing between retry attempts: Cancelling an active attempt does not stop future retries · case 05
Cancelling an active attempt does not stop future retries
Late response fencing between retry attempts: Retry after logical cancellation is reported as a transport lifecycle result · case 01
Retry after logical cancellation is reported as a transport lifecycle result
Late response fencing between retry attempts: Retry after logical cancellation is reported as a transport lifecycle result · case 02
Retry after logical cancellation is reported as a transport lifecycle result
Late response fencing between retry attempts: Retry after logical cancellation is reported as a transport lifecycle result · case 03
Retry after logical cancellation is reported as a transport lifecycle result
Late response fencing between retry attempts: Retry after logical cancellation is reported as a transport lifecycle result · case 04
Retry after logical cancellation is reported as a transport lifecycle result
Late response fencing between retry attempts: Retry after logical cancellation is reported as a transport lifecycle result · case 05
Retry after logical cancellation is reported as a transport lifecycle result
Late response fencing between retry attempts: A completion with a mismatched generation is accepted · case 01
A completion with a mismatched generation is accepted
Late response fencing between retry attempts: A completion with a mismatched generation is accepted · case 02
A completion with a mismatched generation is accepted
Late response fencing between retry attempts: A completion with a mismatched generation is accepted · case 03
A completion with a mismatched generation is accepted
Late response fencing between retry attempts: A completion with a mismatched generation is accepted · case 04
A completion with a mismatched generation is accepted
Late response fencing between retry attempts: A completion with a mismatched generation is accepted · case 05
A completion with a mismatched generation is accepted
Late response fencing between retry attempts: A timed-out attempt can publish a late success · case 01
A timed-out attempt can publish a late success
Late response fencing between retry attempts: A timed-out attempt can publish a late success · case 02
A timed-out attempt can publish a late success
Late response fencing between retry attempts: A timed-out attempt can publish a late success · case 03
A timed-out attempt can publish a late success
Late response fencing between retry attempts: A timed-out attempt can publish a late success · case 04
A timed-out attempt can publish a late success
Late response fencing between retry attempts: A timed-out attempt can publish a late success · case 05
A timed-out attempt can publish a late success
Late response fencing between retry attempts: Duplicate completion of the winning attempt is published twice · case 01
Duplicate completion of the winning attempt is published twice
Late response fencing between retry attempts: Duplicate completion of the winning attempt is published twice · case 02
Duplicate completion of the winning attempt is published twice
Late response fencing between retry attempts: Duplicate completion of the winning attempt is published twice · case 03
Duplicate completion of the winning attempt is published twice
Late response fencing between retry attempts: Duplicate completion of the winning attempt is published twice · case 04
Duplicate completion of the winning attempt is published twice
Late response fencing between retry attempts: Duplicate completion of the winning attempt is published twice · case 05
Duplicate completion of the winning attempt is published twice
Late response fencing between retry attempts: A response arriving after cancellation has the wrong terminal disposition · case 01
A response arriving after cancellation has the wrong terminal disposition
Late response fencing between retry attempts: A response arriving after cancellation has the wrong terminal disposition · case 02
A response arriving after cancellation has the wrong terminal disposition
Late response fencing between retry attempts: A response arriving after cancellation has the wrong terminal disposition · case 03
A response arriving after cancellation has the wrong terminal disposition
Late response fencing between retry attempts: A response arriving after cancellation has the wrong terminal disposition · case 04
A response arriving after cancellation has the wrong terminal disposition
Late response fencing between retry attempts: A response arriving after cancellation has the wrong terminal disposition · case 05
A response arriving after cancellation has the wrong terminal disposition
Late response fencing between retry attempts: A fenced retry response returns its attempt identity instead of its payload · case 01
A fenced retry response returns its attempt identity instead of its payload
Late response fencing between retry attempts: A fenced retry response returns its attempt identity instead of its payload · case 02
A fenced retry response returns its attempt identity instead of its payload
Late response fencing between retry attempts: A fenced retry response returns its attempt identity instead of its payload · case 03
A fenced retry response returns its attempt identity instead of its payload
Late response fencing between retry attempts: A fenced retry response returns its attempt identity instead of its payload · case 04
A fenced retry response returns its attempt identity instead of its payload
Late response fencing between retry attempts: A fenced retry response returns its attempt identity instead of its payload · case 05
A fenced retry response returns its attempt identity instead of its payload
Retry reconciliation with a server receipt: Retry receipts collide across logical operation keys · case 01
Retry receipts collide across logical operation keys
Retry reconciliation with a server receipt: Retry receipts collide across logical operation keys · case 02
Retry receipts collide across logical operation keys
Retry reconciliation with a server receipt: Retry receipts collide across logical operation keys · case 03
Retry receipts collide across logical operation keys
Retry reconciliation with a server receipt: Retry receipts collide across logical operation keys · case 04
Retry receipts collide across logical operation keys
Retry reconciliation with a server receipt: Retry receipts collide across logical operation keys · case 05
Retry receipts collide across logical operation keys
Retry reconciliation with a server receipt: Receipt binding loses the original request representation · case 01
Receipt binding loses the original request representation
Retry reconciliation with a server receipt: Receipt binding loses the original request representation · case 02
Receipt binding loses the original request representation
Retry reconciliation with a server receipt: Receipt binding loses the original request representation · case 03
Receipt binding loses the original request representation
Retry reconciliation with a server receipt: Receipt binding loses the original request representation · case 04
Receipt binding loses the original request representation
Retry reconciliation with a server receipt: Receipt binding loses the original request representation · case 05
Receipt binding loses the original request representation
Retry reconciliation with a server receipt: An in-flight retry receipt is treated as committed · case 01
An in-flight retry receipt is treated as committed
Retry reconciliation with a server receipt: An in-flight retry receipt is treated as committed · case 02
An in-flight retry receipt is treated as committed
Retry reconciliation with a server receipt: An in-flight retry receipt is treated as committed · case 03
An in-flight retry receipt is treated as committed
Retry reconciliation with a server receipt: An in-flight retry receipt is treated as committed · case 04
An in-flight retry receipt is treated as committed
Retry reconciliation with a server receipt: An in-flight retry receipt is treated as committed · case 05
An in-flight retry receipt is treated as committed
Retry reconciliation with a server receipt: Reusing an idempotency key for changed content replays an unrelated result · case 01
Reusing an idempotency key for changed content replays an unrelated result
Retry reconciliation with a server receipt: Reusing an idempotency key for changed content replays an unrelated result · case 02
Reusing an idempotency key for changed content replays an unrelated result
Retry reconciliation with a server receipt: Reusing an idempotency key for changed content replays an unrelated result · case 03
Reusing an idempotency key for changed content replays an unrelated result
Retry reconciliation with a server receipt: Reusing an idempotency key for changed content replays an unrelated result · case 04
Reusing an idempotency key for changed content replays an unrelated result
Retry reconciliation with a server receipt: Reusing an idempotency key for changed content replays an unrelated result · case 05
Reusing an idempotency key for changed content replays an unrelated result
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 ↗