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
Acknowledge a replicated write concern: Repeated acknowledgements count as separate replicas · case 01
The write concern operation is admitted even though repeated acknowledgements count as separate replicas.
Acknowledge a replicated write concern: Repeated acknowledgements count as separate replicas · case 02
The write concern operation is admitted even though repeated acknowledgements count as separate replicas.
Acknowledge a replicated write concern: Repeated acknowledgements count as separate replicas · case 03
The write concern operation is admitted even though repeated acknowledgements count as separate replicas.
Acknowledge a replicated write concern: Repeated acknowledgements count as separate replicas · case 04
The write concern operation is admitted even though repeated acknowledgements count as separate replicas.
Acknowledge a replicated write concern: Repeated acknowledgements count as separate replicas · case 05
The write concern operation is admitted even though repeated acknowledgements count as separate replicas.
Acknowledge a replicated write concern: Volatile receipt acknowledgements satisfy durable concern · case 01
The write concern operation is admitted even though volatile receipt acknowledgements satisfy durable concern.
Acknowledge a replicated write concern: Volatile receipt acknowledgements satisfy durable concern · case 02
The write concern operation is admitted even though volatile receipt acknowledgements satisfy durable concern.
Acknowledge a replicated write concern: Volatile receipt acknowledgements satisfy durable concern · case 03
The write concern operation is admitted even though volatile receipt acknowledgements satisfy durable concern.
Acknowledge a replicated write concern: Volatile receipt acknowledgements satisfy durable concern · case 04
The write concern operation is admitted even though volatile receipt acknowledgements satisfy durable concern.
Acknowledge a replicated write concern: Volatile receipt acknowledgements satisfy durable concern · case 05
The write concern operation is admitted even though volatile receipt acknowledgements satisfy durable concern.
Acknowledge a replicated write concern: Multiple copies in one failure domain satisfy zone concern · case 01
The write concern operation is admitted even though multiple copies in one failure domain satisfy zone concern.
Acknowledge a replicated write concern: Multiple copies in one failure domain satisfy zone concern · case 02
The write concern operation is admitted even though multiple copies in one failure domain satisfy zone concern.
Acknowledge a replicated write concern: Multiple copies in one failure domain satisfy zone concern · case 03
The write concern operation is admitted even though multiple copies in one failure domain satisfy zone concern.
Acknowledge a replicated write concern: Multiple copies in one failure domain satisfy zone concern · case 04
The write concern operation is admitted even though multiple copies in one failure domain satisfy zone concern.
Acknowledge a replicated write concern: Multiple copies in one failure domain satisfy zone concern · case 05
The write concern operation is admitted even though multiple copies in one failure domain satisfy zone concern.
Acknowledge a replicated write concern: Replica acknowledgements refer to another write · case 01
The write concern operation is admitted even though replica acknowledgements refer to another write.
Acknowledge a replicated write concern: Replica acknowledgements refer to another write · case 02
The write concern operation is admitted even though replica acknowledgements refer to another write.
Acknowledge a replicated write concern: Replica acknowledgements refer to another write · case 03
The write concern operation is admitted even though replica acknowledgements refer to another write.
Acknowledge a replicated write concern: Replica acknowledgements refer to another write · case 04
The write concern operation is admitted even though replica acknowledgements refer to another write.
Acknowledge a replicated write concern: Replica acknowledgements refer to another write · case 05
The write concern operation is admitted even though replica acknowledgements refer to another write.
Acknowledge a replicated write concern: A write is reported successful after its response deadline · case 01
The write concern operation is admitted even though a write is reported successful after its response deadline.
Acknowledge a replicated write concern: A write is reported successful after its response deadline · case 02
The write concern operation is admitted even though a write is reported successful after its response deadline.
Acknowledge a replicated write concern: A write is reported successful after its response deadline · case 03
The write concern operation is admitted even though a write is reported successful after its response deadline.
Acknowledge a replicated write concern: A write is reported successful after its response deadline · case 04
The write concern operation is admitted even though a write is reported successful after its response deadline.
Acknowledge a replicated write concern: A write is reported successful after its response deadline · case 05
The write concern operation is admitted even though a write is reported successful after its response deadline.
Accept a durable queue publication: An oversized message bypasses broker frame limits · case 01
The queue publish operation is admitted even though an oversized message bypasses broker frame limits.
Accept a durable queue publication: An oversized message bypasses broker frame limits · case 02
The queue publish operation is admitted even though an oversized message bypasses broker frame limits.
Accept a durable queue publication: An oversized message bypasses broker frame limits · case 03
The queue publish operation is admitted even though an oversized message bypasses broker frame limits.
Accept a durable queue publication: An oversized message bypasses broker frame limits · case 04
The queue publish operation is admitted even though an oversized message bypasses broker frame limits.
Accept a durable queue publication: An oversized message bypasses broker frame limits · case 05
The queue publish operation is admitted even though an oversized message bypasses broker frame limits.
Accept a durable queue publication: Admission exceeds the queue retained-byte budget · case 01
The queue publish operation is admitted even though admission exceeds the queue retained-byte budget.
Accept a durable queue publication: Admission exceeds the queue retained-byte budget · case 02
The queue publish operation is admitted even though admission exceeds the queue retained-byte budget.
Accept a durable queue publication: Admission exceeds the queue retained-byte budget · case 03
The queue publish operation is admitted even though admission exceeds the queue retained-byte budget.
Accept a durable queue publication: Admission exceeds the queue retained-byte budget · case 04
The queue publish operation is admitted even though admission exceeds the queue retained-byte budget.
Accept a durable queue publication: Admission exceeds the queue retained-byte budget · case 05
The queue publish operation is admitted even though admission exceeds the queue retained-byte budget.
Accept a durable queue publication: A mandatory message has no matching queue · case 01
The queue publish operation is admitted even though a mandatory message has no matching queue.
Accept a durable queue publication: A mandatory message has no matching queue · case 02
The queue publish operation is admitted even though a mandatory message has no matching queue.
Accept a durable queue publication: A mandatory message has no matching queue · case 03
The queue publish operation is admitted even though a mandatory message has no matching queue.
Accept a durable queue publication: A mandatory message has no matching queue · case 04
The queue publish operation is admitted even though a mandatory message has no matching queue.
Accept a durable queue publication: A mandatory message has no matching queue · case 05
The queue publish operation is admitted even though a mandatory message has no matching queue.
Accept a durable queue publication: A fenced producer continues publishing · case 01
The queue publish operation is admitted even though a fenced producer continues publishing.
Accept a durable queue publication: A fenced producer continues publishing · case 02
The queue publish operation is admitted even though a fenced producer continues publishing.
Accept a durable queue publication: A fenced producer continues publishing · case 03
The queue publish operation is admitted even though a fenced producer continues publishing.
Accept a durable queue publication: A fenced producer continues publishing · case 04
The queue publish operation is admitted even though a fenced producer continues publishing.
Accept a durable queue publication: A fenced producer continues publishing · case 05
The queue publish operation is admitted even though a fenced producer continues publishing.
Accept a durable queue publication: A producer sequence gap is accepted as contiguous · case 01
The queue publish operation is admitted even though a producer sequence gap is accepted as contiguous.
Accept a durable queue publication: A producer sequence gap is accepted as contiguous · case 02
The queue publish operation is admitted even though a producer sequence gap is accepted as contiguous.
Accept a durable queue publication: A producer sequence gap is accepted as contiguous · case 03
The queue publish operation is admitted even though a producer sequence gap is accepted as contiguous.
Accept a durable queue publication: A producer sequence gap is accepted as contiguous · case 04
The queue publish operation is admitted even though a producer sequence gap is accepted as contiguous.
Accept a durable queue publication: A producer sequence gap is accepted as contiguous · case 05
The queue publish operation is admitted even though a producer sequence gap is accepted as contiguous.
Reserve a queued message for delivery: A scheduled message is delivered before its visibility instant · case 01
The queue reservation operation is admitted even though a scheduled message is delivered before its visibility instant.
Reserve a queued message for delivery: A scheduled message is delivered before its visibility instant · case 02
The queue reservation operation is admitted even though a scheduled message is delivered before its visibility instant.
Reserve a queued message for delivery: A scheduled message is delivered before its visibility instant · case 03
The queue reservation operation is admitted even though a scheduled message is delivered before its visibility instant.
Reserve a queued message for delivery: A scheduled message is delivered before its visibility instant · case 04
The queue reservation operation is admitted even though a scheduled message is delivered before its visibility instant.
Reserve a queued message for delivery: A scheduled message is delivered before its visibility instant · case 05
The queue reservation operation is admitted even though a scheduled message is delivered before its visibility instant.
Reserve a queued message for delivery: A message is delivered after its expiration deadline · case 01
The queue reservation operation is admitted even though a message is delivered after its expiration deadline.
Reserve a queued message for delivery: A message is delivered after its expiration deadline · case 02
The queue reservation operation is admitted even though a message is delivered after its expiration deadline.
Reserve a queued message for delivery: A message is delivered after its expiration deadline · case 03
The queue reservation operation is admitted even though a message is delivered after its expiration deadline.
Reserve a queued message for delivery: A message is delivered after its expiration deadline · case 04
The queue reservation operation is admitted even though a message is delivered after its expiration deadline.
Reserve a queued message for delivery: A message is delivered after its expiration deadline · case 05
The queue reservation operation is admitted even though a message is delivered after its expiration deadline.
Reserve a queued message for delivery: A second worker reserves a currently leased message · case 01
The queue reservation operation is admitted even though a second worker reserves a currently leased message.
Reserve a queued message for delivery: A second worker reserves a currently leased message · case 02
The queue reservation operation is admitted even though a second worker reserves a currently leased message.
Reserve a queued message for delivery: A second worker reserves a currently leased message · case 03
The queue reservation operation is admitted even though a second worker reserves a currently leased message.
Reserve a queued message for delivery: A second worker reserves a currently leased message · case 04
The queue reservation operation is admitted even though a second worker reserves a currently leased message.
Reserve a queued message for delivery: A second worker reserves a currently leased message · case 05
The queue reservation operation is admitted even though a second worker reserves a currently leased message.
Reserve a queued message for delivery: The broker exceeds consumer in-flight credit · case 01
The queue reservation operation is admitted even though the broker exceeds consumer in-flight credit.
Reserve a queued message for delivery: The broker exceeds consumer in-flight credit · case 02
The queue reservation operation is admitted even though the broker exceeds consumer in-flight credit.
Reserve a queued message for delivery: The broker exceeds consumer in-flight credit · case 03
The queue reservation operation is admitted even though the broker exceeds consumer in-flight credit.
Reserve a queued message for delivery: The broker exceeds consumer in-flight credit · case 04
The queue reservation operation is admitted even though the broker exceeds consumer in-flight credit.
Reserve a queued message for delivery: The broker exceeds consumer in-flight credit · case 05
The queue reservation operation is admitted even though the broker exceeds consumer in-flight credit.
Reserve a queued message for delivery: A FIFO message overtakes an earlier group member · case 01
The queue reservation operation is admitted even though a fifo message overtakes an earlier group member.
Reserve a queued message for delivery: A FIFO message overtakes an earlier group member · case 02
The queue reservation operation is admitted even though a fifo message overtakes an earlier group member.
Reserve a queued message for delivery: A FIFO message overtakes an earlier group member · case 03
The queue reservation operation is admitted even though a fifo message overtakes an earlier group member.
Reserve a queued message for delivery: A FIFO message overtakes an earlier group member · case 04
The queue reservation operation is admitted even though a fifo message overtakes an earlier group member.
Reserve a queued message for delivery: A FIFO message overtakes an earlier group member · case 05
The queue reservation operation is admitted even though a fifo message overtakes an earlier group member.
Settle a queue delivery acknowledgement: A receipt from an older delivery deletes the current message · case 01
The queue acknowledge operation is admitted even though a receipt from an older delivery deletes the current message.
Settle a queue delivery acknowledgement: A receipt from an older delivery deletes the current message · case 02
The queue acknowledge operation is admitted even though a receipt from an older delivery deletes the current message.
Settle a queue delivery acknowledgement: A receipt from an older delivery deletes the current message · case 03
The queue acknowledge operation is admitted even though a receipt from an older delivery deletes the current message.
Settle a queue delivery acknowledgement: A receipt from an older delivery deletes the current message · case 04
The queue acknowledge operation is admitted even though a receipt from an older delivery deletes the current message.
Settle a queue delivery acknowledgement: A receipt from an older delivery deletes the current message · case 05
The queue acknowledge operation is admitted even though a receipt from an older delivery deletes the current message.
Settle a queue delivery acknowledgement: An acknowledgement settles an already expired reservation · case 01
The queue acknowledge operation is admitted even though an acknowledgement settles an already expired reservation.
Settle a queue delivery acknowledgement: An acknowledgement settles an already expired reservation · case 02
The queue acknowledge operation is admitted even though an acknowledgement settles an already expired reservation.
Settle a queue delivery acknowledgement: An acknowledgement settles an already expired reservation · case 03
The queue acknowledge operation is admitted even though an acknowledgement settles an already expired reservation.
Settle a queue delivery acknowledgement: An acknowledgement settles an already expired reservation · case 04
The queue acknowledge operation is admitted even though an acknowledgement settles an already expired reservation.
Settle a queue delivery acknowledgement: An acknowledgement settles an already expired reservation · case 05
The queue acknowledge operation is admitted even though an acknowledgement settles an already expired reservation.
Settle a queue delivery acknowledgement: A delivery tag from another channel is settled · case 01
The queue acknowledge operation is admitted even though a delivery tag from another channel is settled.
Settle a queue delivery acknowledgement: A delivery tag from another channel is settled · case 02
The queue acknowledge operation is admitted even though a delivery tag from another channel is settled.
Settle a queue delivery acknowledgement: A delivery tag from another channel is settled · case 03
The queue acknowledge operation is admitted even though a delivery tag from another channel is settled.
Settle a queue delivery acknowledgement: A delivery tag from another channel is settled · case 04
The queue acknowledge operation is admitted even though a delivery tag from another channel is settled.
Settle a queue delivery acknowledgement: A delivery tag from another channel is settled · case 05
The queue acknowledge operation is admitted even though a delivery tag from another channel is settled.
Settle a queue delivery acknowledgement: A second settlement credits the consumer twice · case 01
The queue acknowledge operation is admitted even though a second settlement credits the consumer twice.
Settle a queue delivery acknowledgement: A second settlement credits the consumer twice · case 02
The queue acknowledge operation is admitted even though a second settlement credits the consumer twice.
Settle a queue delivery acknowledgement: A second settlement credits the consumer twice · case 03
The queue acknowledge operation is admitted even though a second settlement credits the consumer twice.
Settle a queue delivery acknowledgement: A second settlement credits the consumer twice · case 04
The queue acknowledge operation is admitted even though a second settlement credits the consumer twice.
Settle a queue delivery acknowledgement: A second settlement credits the consumer twice · case 05
The queue acknowledge operation is admitted even though a second settlement credits the consumer twice.
Settle a queue delivery acknowledgement: Cumulative acknowledgement jumps over an unprocessed delivery · case 01
The queue acknowledge operation is admitted even though cumulative acknowledgement jumps over an unprocessed delivery.
Settle a queue delivery acknowledgement: Cumulative acknowledgement jumps over an unprocessed delivery · case 02
The queue acknowledge operation is admitted even though cumulative acknowledgement jumps over an unprocessed delivery.
Settle a queue delivery acknowledgement: Cumulative acknowledgement jumps over an unprocessed delivery · case 03
The queue acknowledge operation is admitted even though cumulative acknowledgement jumps over an unprocessed delivery.
Settle a queue delivery acknowledgement: Cumulative acknowledgement jumps over an unprocessed delivery · case 04
The queue acknowledge operation is admitted even though cumulative acknowledgement jumps over an unprocessed delivery.
Settle a queue delivery acknowledgement: Cumulative acknowledgement jumps over an unprocessed delivery · case 05
The queue acknowledge operation is admitted even though cumulative acknowledgement jumps over an unprocessed delivery.
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 ↗