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
Move a poison message to a dead-letter queue: A transient first failure is dead-lettered prematurely · case 01
The queue dead letter operation is admitted even though a transient first failure is dead-lettered prematurely.
Move a poison message to a dead-letter queue: A transient first failure is dead-lettered prematurely · case 02
The queue dead letter operation is admitted even though a transient first failure is dead-lettered prematurely.
Move a poison message to a dead-letter queue: A transient first failure is dead-lettered prematurely · case 03
The queue dead letter operation is admitted even though a transient first failure is dead-lettered prematurely.
Move a poison message to a dead-letter queue: A transient first failure is dead-lettered prematurely · case 04
The queue dead letter operation is admitted even though a transient first failure is dead-lettered prematurely.
Move a poison message to a dead-letter queue: A transient first failure is dead-lettered prematurely · case 05
The queue dead letter operation is admitted even though a transient first failure is dead-lettered prematurely.
Move a poison message to a dead-letter queue: The source is deleted without a dead-letter destination · case 01
The queue dead letter operation is admitted even though the source is deleted without a dead-letter destination.
Move a poison message to a dead-letter queue: The source is deleted without a dead-letter destination · case 02
The queue dead letter operation is admitted even though the source is deleted without a dead-letter destination.
Move a poison message to a dead-letter queue: The source is deleted without a dead-letter destination · case 03
The queue dead letter operation is admitted even though the source is deleted without a dead-letter destination.
Move a poison message to a dead-letter queue: The source is deleted without a dead-letter destination · case 04
The queue dead letter operation is admitted even though the source is deleted without a dead-letter destination.
Move a poison message to a dead-letter queue: The source is deleted without a dead-letter destination · case 05
The queue dead letter operation is admitted even though the source is deleted without a dead-letter destination.
Move a poison message to a dead-letter queue: The source is removed before the target copy is durable · case 01
The queue dead letter operation is admitted even though the source is removed before the target copy is durable.
Move a poison message to a dead-letter queue: The source is removed before the target copy is durable · case 02
The queue dead letter operation is admitted even though the source is removed before the target copy is durable.
Move a poison message to a dead-letter queue: The source is removed before the target copy is durable · case 03
The queue dead letter operation is admitted even though the source is removed before the target copy is durable.
Move a poison message to a dead-letter queue: The source is removed before the target copy is durable · case 04
The queue dead letter operation is admitted even though the source is removed before the target copy is durable.
Move a poison message to a dead-letter queue: The source is removed before the target copy is durable · case 05
The queue dead letter operation is admitted even though the source is removed before the target copy is durable.
Move a poison message to a dead-letter queue: Dead-letter forwarding revisits a queue in its own route · case 01
The queue dead letter operation is admitted even though dead-letter forwarding revisits a queue in its own route.
Move a poison message to a dead-letter queue: Dead-letter forwarding revisits a queue in its own route · case 02
The queue dead letter operation is admitted even though dead-letter forwarding revisits a queue in its own route.
Move a poison message to a dead-letter queue: Dead-letter forwarding revisits a queue in its own route · case 03
The queue dead letter operation is admitted even though dead-letter forwarding revisits a queue in its own route.
Move a poison message to a dead-letter queue: Dead-letter forwarding revisits a queue in its own route · case 04
The queue dead letter operation is admitted even though dead-letter forwarding revisits a queue in its own route.
Move a poison message to a dead-letter queue: Dead-letter forwarding revisits a queue in its own route · case 05
The queue dead letter operation is admitted even though dead-letter forwarding revisits a queue in its own route.
Move a poison message to a dead-letter queue: Dead-letter transfer loses the original message identity · case 01
The queue dead letter operation is admitted even though dead-letter transfer loses the original message identity.
Move a poison message to a dead-letter queue: Dead-letter transfer loses the original message identity · case 02
The queue dead letter operation is admitted even though dead-letter transfer loses the original message identity.
Move a poison message to a dead-letter queue: Dead-letter transfer loses the original message identity · case 03
The queue dead letter operation is admitted even though dead-letter transfer loses the original message identity.
Move a poison message to a dead-letter queue: Dead-letter transfer loses the original message identity · case 04
The queue dead letter operation is admitted even though dead-letter transfer loses the original message identity.
Move a poison message to a dead-letter queue: Dead-letter transfer loses the original message identity · case 05
The queue dead letter operation is admitted even though dead-letter transfer loses the original message identity.
Redrive a previously dead-lettered message: Poison messages circulate past the redrive allowance · case 01
The queue redrive operation is admitted even though poison messages circulate past the redrive allowance.
Redrive a previously dead-lettered message: Poison messages circulate past the redrive allowance · case 02
The queue redrive operation is admitted even though poison messages circulate past the redrive allowance.
Redrive a previously dead-lettered message: Poison messages circulate past the redrive allowance · case 03
The queue redrive operation is admitted even though poison messages circulate past the redrive allowance.
Redrive a previously dead-lettered message: Poison messages circulate past the redrive allowance · case 04
The queue redrive operation is admitted even though poison messages circulate past the redrive allowance.
Redrive a previously dead-lettered message: Poison messages circulate past the redrive allowance · case 05
The queue redrive operation is admitted even though poison messages circulate past the redrive allowance.
Redrive a previously dead-lettered message: Redrive races an updated dead-letter record · case 01
The queue redrive operation is admitted even though redrive races an updated dead-letter record.
Redrive a previously dead-lettered message: Redrive races an updated dead-letter record · case 02
The queue redrive operation is admitted even though redrive races an updated dead-letter record.
Redrive a previously dead-lettered message: Redrive races an updated dead-letter record · case 03
The queue redrive operation is admitted even though redrive races an updated dead-letter record.
Redrive a previously dead-lettered message: Redrive races an updated dead-letter record · case 04
The queue redrive operation is admitted even though redrive races an updated dead-letter record.
Redrive a previously dead-lettered message: Redrive races an updated dead-letter record · case 05
The queue redrive operation is admitted even though redrive races an updated dead-letter record.
Redrive a previously dead-lettered message: The target consumer cannot decode the original schema · case 01
The queue redrive operation is admitted even though the target consumer cannot decode the original schema.
Redrive a previously dead-lettered message: The target consumer cannot decode the original schema · case 02
The queue redrive operation is admitted even though the target consumer cannot decode the original schema.
Redrive a previously dead-lettered message: The target consumer cannot decode the original schema · case 03
The queue redrive operation is admitted even though the target consumer cannot decode the original schema.
Redrive a previously dead-lettered message: The target consumer cannot decode the original schema · case 04
The queue redrive operation is admitted even though the target consumer cannot decode the original schema.
Redrive a previously dead-lettered message: The target consumer cannot decode the original schema · case 05
The queue redrive operation is admitted even though the target consumer cannot decode the original schema.
Redrive a previously dead-lettered message: Redrive revives a message past its absolute retention · case 01
The queue redrive operation is admitted even though redrive revives a message past its absolute retention.
Redrive a previously dead-lettered message: Redrive revives a message past its absolute retention · case 02
The queue redrive operation is admitted even though redrive revives a message past its absolute retention.
Redrive a previously dead-lettered message: Redrive revives a message past its absolute retention · case 03
The queue redrive operation is admitted even though redrive revives a message past its absolute retention.
Redrive a previously dead-lettered message: Redrive revives a message past its absolute retention · case 04
The queue redrive operation is admitted even though redrive revives a message past its absolute retention.
Redrive a previously dead-lettered message: Redrive revives a message past its absolute retention · case 05
The queue redrive operation is admitted even though redrive revives a message past its absolute retention.
Redrive a previously dead-lettered message: Redrive bypasses its recovery traffic budget · case 01
The queue redrive operation is admitted even though redrive bypasses its recovery traffic budget.
Redrive a previously dead-lettered message: Redrive bypasses its recovery traffic budget · case 02
The queue redrive operation is admitted even though redrive bypasses its recovery traffic budget.
Redrive a previously dead-lettered message: Redrive bypasses its recovery traffic budget · case 03
The queue redrive operation is admitted even though redrive bypasses its recovery traffic budget.
Redrive a previously dead-lettered message: Redrive bypasses its recovery traffic budget · case 04
The queue redrive operation is admitted even though redrive bypasses its recovery traffic budget.
Redrive a previously dead-lettered message: Redrive bypasses its recovery traffic budget · case 05
The queue redrive operation is admitted even though redrive bypasses its recovery traffic budget.
Assign a partition during consumer rebalance: The new consumer starts while the old owner remains active · case 01
The partition rebalance operation is admitted even though the new consumer starts while the old owner remains active.
Assign a partition during consumer rebalance: The new consumer starts while the old owner remains active · case 02
The partition rebalance operation is admitted even though the new consumer starts while the old owner remains active.
Assign a partition during consumer rebalance: The new consumer starts while the old owner remains active · case 03
The partition rebalance operation is admitted even though the new consumer starts while the old owner remains active.
Assign a partition during consumer rebalance: The new consumer starts while the old owner remains active · case 04
The partition rebalance operation is admitted even though the new consumer starts while the old owner remains active.
Assign a partition during consumer rebalance: The new consumer starts while the old owner remains active · case 05
The partition rebalance operation is admitted even though the new consumer starts while the old owner remains active.
Assign a partition during consumer rebalance: A stale rebalance overwrites a newer assignment · case 01
The partition rebalance operation is admitted even though a stale rebalance overwrites a newer assignment.
Assign a partition during consumer rebalance: A stale rebalance overwrites a newer assignment · case 02
The partition rebalance operation is admitted even though a stale rebalance overwrites a newer assignment.
Assign a partition during consumer rebalance: A stale rebalance overwrites a newer assignment · case 03
The partition rebalance operation is admitted even though a stale rebalance overwrites a newer assignment.
Assign a partition during consumer rebalance: A stale rebalance overwrites a newer assignment · case 04
The partition rebalance operation is admitted even though a stale rebalance overwrites a newer assignment.
Assign a partition during consumer rebalance: A stale rebalance overwrites a newer assignment · case 05
The partition rebalance operation is admitted even though a stale rebalance overwrites a newer assignment.
Assign a partition during consumer rebalance: A new owner starts without the last committed checkpoint · case 01
The partition rebalance operation is admitted even though a new owner starts without the last committed checkpoint.
Assign a partition during consumer rebalance: A new owner starts without the last committed checkpoint · case 02
The partition rebalance operation is admitted even though a new owner starts without the last committed checkpoint.
Assign a partition during consumer rebalance: A new owner starts without the last committed checkpoint · case 03
The partition rebalance operation is admitted even though a new owner starts without the last committed checkpoint.
Assign a partition during consumer rebalance: A new owner starts without the last committed checkpoint · case 04
The partition rebalance operation is admitted even though a new owner starts without the last committed checkpoint.
Assign a partition during consumer rebalance: A new owner starts without the last committed checkpoint · case 05
The partition rebalance operation is admitted even though a new owner starts without the last committed checkpoint.
Assign a partition during consumer rebalance: A partition is assigned to a consumer not subscribed to its topic · case 01
The partition rebalance operation is admitted even though a partition is assigned to a consumer not subscribed to its topic.
Assign a partition during consumer rebalance: A partition is assigned to a consumer not subscribed to its topic · case 02
The partition rebalance operation is admitted even though a partition is assigned to a consumer not subscribed to its topic.
Assign a partition during consumer rebalance: A partition is assigned to a consumer not subscribed to its topic · case 03
The partition rebalance operation is admitted even though a partition is assigned to a consumer not subscribed to its topic.
Assign a partition during consumer rebalance: A partition is assigned to a consumer not subscribed to its topic · case 04
The partition rebalance operation is admitted even though a partition is assigned to a consumer not subscribed to its topic.
Assign a partition during consumer rebalance: A partition is assigned to a consumer not subscribed to its topic · case 05
The partition rebalance operation is admitted even though a partition is assigned to a consumer not subscribed to its topic.
Assign a partition during consumer rebalance: Rebalance exceeds the new owner partition capacity · case 01
The partition rebalance operation is admitted even though rebalance exceeds the new owner partition capacity.
Assign a partition during consumer rebalance: Rebalance exceeds the new owner partition capacity · case 02
The partition rebalance operation is admitted even though rebalance exceeds the new owner partition capacity.
Assign a partition during consumer rebalance: Rebalance exceeds the new owner partition capacity · case 03
The partition rebalance operation is admitted even though rebalance exceeds the new owner partition capacity.
Assign a partition during consumer rebalance: Rebalance exceeds the new owner partition capacity · case 04
The partition rebalance operation is admitted even though rebalance exceeds the new owner partition capacity.
Assign a partition during consumer rebalance: Rebalance exceeds the new owner partition capacity · case 05
The partition rebalance operation is admitted even though rebalance exceeds the new owner partition capacity.
Commit a consume-transform-publish transaction: Commit acknowledges an input partition no longer owned · case 01
The transactional consume operation is admitted even though commit acknowledges an input partition no longer owned.
Commit a consume-transform-publish transaction: Commit acknowledges an input partition no longer owned · case 02
The transactional consume operation is admitted even though commit acknowledges an input partition no longer owned.
Commit a consume-transform-publish transaction: Commit acknowledges an input partition no longer owned · case 03
The transactional consume operation is admitted even though commit acknowledges an input partition no longer owned.
Commit a consume-transform-publish transaction: Commit acknowledges an input partition no longer owned · case 04
The transactional consume operation is admitted even though commit acknowledges an input partition no longer owned.
Commit a consume-transform-publish transaction: Commit acknowledges an input partition no longer owned · case 05
The transactional consume operation is admitted even though commit acknowledges an input partition no longer owned.
Commit a consume-transform-publish transaction: Input progress commits before the transformed output · case 01
The transactional consume operation is admitted even though input progress commits before the transformed output.
Commit a consume-transform-publish transaction: Input progress commits before the transformed output · case 02
The transactional consume operation is admitted even though input progress commits before the transformed output.
Commit a consume-transform-publish transaction: Input progress commits before the transformed output · case 03
The transactional consume operation is admitted even though input progress commits before the transformed output.
Commit a consume-transform-publish transaction: Input progress commits before the transformed output · case 04
The transactional consume operation is admitted even though input progress commits before the transformed output.
Commit a consume-transform-publish transaction: Input progress commits before the transformed output · case 05
The transactional consume operation is admitted even though input progress commits before the transformed output.
Commit a consume-transform-publish transaction: Commit skips an unprocessed input offset · case 01
The transactional consume operation is admitted even though commit skips an unprocessed input offset.
Commit a consume-transform-publish transaction: Commit skips an unprocessed input offset · case 02
The transactional consume operation is admitted even though commit skips an unprocessed input offset.
Commit a consume-transform-publish transaction: Commit skips an unprocessed input offset · case 03
The transactional consume operation is admitted even though commit skips an unprocessed input offset.
Commit a consume-transform-publish transaction: Commit skips an unprocessed input offset · case 04
The transactional consume operation is admitted even though commit skips an unprocessed input offset.
Commit a consume-transform-publish transaction: Commit skips an unprocessed input offset · case 05
The transactional consume operation is admitted even though commit skips an unprocessed input offset.
Commit a consume-transform-publish transaction: A commit revives an aborted consume transaction · case 01
The transactional consume operation is admitted even though a commit revives an aborted consume transaction.
Commit a consume-transform-publish transaction: A commit revives an aborted consume transaction · case 02
The transactional consume operation is admitted even though a commit revives an aborted consume transaction.
Commit a consume-transform-publish transaction: A commit revives an aborted consume transaction · case 03
The transactional consume operation is admitted even though a commit revives an aborted consume transaction.
Commit a consume-transform-publish transaction: A commit revives an aborted consume transaction · case 04
The transactional consume operation is admitted even though a commit revives an aborted consume transaction.
Commit a consume-transform-publish transaction: A commit revives an aborted consume transaction · case 05
The transactional consume operation is admitted even though a commit revives an aborted consume transaction.
Commit a consume-transform-publish transaction: A previous producer instance commits an old transaction · case 01
The transactional consume operation is admitted even though a previous producer instance commits an old transaction.
Commit a consume-transform-publish transaction: A previous producer instance commits an old transaction · case 02
The transactional consume operation is admitted even though a previous producer instance commits an old transaction.
Commit a consume-transform-publish transaction: A previous producer instance commits an old transaction · case 03
The transactional consume operation is admitted even though a previous producer instance commits an old transaction.
Commit a consume-transform-publish transaction: A previous producer instance commits an old transaction · case 04
The transactional consume operation is admitted even though a previous producer instance commits an old transaction.
Commit a consume-transform-publish transaction: A previous producer instance commits an old transaction · case 05
The transactional consume operation is admitted even though a previous producer instance commits an old transaction.
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 ↗