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
Persist a replication resume checkpoint: The resume point crosses an unapplied sequence gap · case 01
The replication checkpoint operation is admitted even though the resume point crosses an unapplied sequence gap.
Persist a replication resume checkpoint: The resume point crosses an unapplied sequence gap · case 02
The replication checkpoint operation is admitted even though the resume point crosses an unapplied sequence gap.
Persist a replication resume checkpoint: The resume point crosses an unapplied sequence gap · case 03
The replication checkpoint operation is admitted even though the resume point crosses an unapplied sequence gap.
Persist a replication resume checkpoint: The resume point crosses an unapplied sequence gap · case 04
The replication checkpoint operation is admitted even though the resume point crosses an unapplied sequence gap.
Persist a replication resume checkpoint: The resume point crosses an unapplied sequence gap · case 05
The replication checkpoint operation is admitted even though the resume point crosses an unapplied sequence gap.
Persist a replication resume checkpoint: A checkpoint is reused after the source log is recreated · case 01
The replication checkpoint operation is admitted even though a checkpoint is reused after the source log is recreated.
Persist a replication resume checkpoint: A checkpoint is reused after the source log is recreated · case 02
The replication checkpoint operation is admitted even though a checkpoint is reused after the source log is recreated.
Persist a replication resume checkpoint: A checkpoint is reused after the source log is recreated · case 03
The replication checkpoint operation is admitted even though a checkpoint is reused after the source log is recreated.
Persist a replication resume checkpoint: A checkpoint is reused after the source log is recreated · case 04
The replication checkpoint operation is admitted even though a checkpoint is reused after the source log is recreated.
Persist a replication resume checkpoint: A checkpoint is reused after the source log is recreated · case 05
The replication checkpoint operation is admitted even though a checkpoint is reused after the source log is recreated.
Persist a replication resume checkpoint: The checkpoint exceeds durable destination progress · case 01
The replication checkpoint operation is admitted even though the checkpoint exceeds durable destination progress.
Persist a replication resume checkpoint: The checkpoint exceeds durable destination progress · case 02
The replication checkpoint operation is admitted even though the checkpoint exceeds durable destination progress.
Persist a replication resume checkpoint: The checkpoint exceeds durable destination progress · case 03
The replication checkpoint operation is admitted even though the checkpoint exceeds durable destination progress.
Persist a replication resume checkpoint: The checkpoint exceeds durable destination progress · case 04
The replication checkpoint operation is admitted even though the checkpoint exceeds durable destination progress.
Persist a replication resume checkpoint: The checkpoint exceeds durable destination progress · case 05
The replication checkpoint operation is admitted even though the checkpoint exceeds durable destination progress.
Persist a replication resume checkpoint: A resume point splits a source transaction · case 01
The replication checkpoint operation is admitted even though a resume point splits a source transaction.
Persist a replication resume checkpoint: A resume point splits a source transaction · case 02
The replication checkpoint operation is admitted even though a resume point splits a source transaction.
Persist a replication resume checkpoint: A resume point splits a source transaction · case 03
The replication checkpoint operation is admitted even though a resume point splits a source transaction.
Persist a replication resume checkpoint: A resume point splits a source transaction · case 04
The replication checkpoint operation is admitted even though a resume point splits a source transaction.
Persist a replication resume checkpoint: A resume point splits a source transaction · case 05
The replication checkpoint operation is admitted even though a resume point splits a source transaction.
Persist a replication resume checkpoint: A delayed checkpoint regresses persisted progress · case 01
The replication checkpoint operation is admitted even though a delayed checkpoint regresses persisted progress.
Persist a replication resume checkpoint: A delayed checkpoint regresses persisted progress · case 02
The replication checkpoint operation is admitted even though a delayed checkpoint regresses persisted progress.
Persist a replication resume checkpoint: A delayed checkpoint regresses persisted progress · case 03
The replication checkpoint operation is admitted even though a delayed checkpoint regresses persisted progress.
Persist a replication resume checkpoint: A delayed checkpoint regresses persisted progress · case 04
The replication checkpoint operation is admitted even though a delayed checkpoint regresses persisted progress.
Persist a replication resume checkpoint: A delayed checkpoint regresses persisted progress · case 05
The replication checkpoint operation is admitted even though a delayed checkpoint regresses persisted progress.
Admit a conflict resolution result: The resolution omits a known conflicting parent · case 01
The conflict resolution operation is admitted even though the resolution omits a known conflicting parent.
Admit a conflict resolution result: The resolution omits a known conflicting parent · case 02
The conflict resolution operation is admitted even though the resolution omits a known conflicting parent.
Admit a conflict resolution result: The resolution omits a known conflicting parent · case 03
The conflict resolution operation is admitted even though the resolution omits a known conflicting parent.
Admit a conflict resolution result: The resolution omits a known conflicting parent · case 04
The conflict resolution operation is admitted even though the resolution omits a known conflicting parent.
Admit a conflict resolution result: The resolution omits a known conflicting parent · case 05
The conflict resolution operation is admitted even though the resolution omits a known conflicting parent.
Admit a conflict resolution result: The resolved clock regresses a parent component · case 01
The conflict resolution operation is admitted even though the resolved clock regresses a parent component.
Admit a conflict resolution result: The resolved clock regresses a parent component · case 02
The conflict resolution operation is admitted even though the resolved clock regresses a parent component.
Admit a conflict resolution result: The resolved clock regresses a parent component · case 03
The conflict resolution operation is admitted even though the resolved clock regresses a parent component.
Admit a conflict resolution result: The resolved clock regresses a parent component · case 04
The conflict resolution operation is admitted even though the resolved clock regresses a parent component.
Admit a conflict resolution result: The resolved clock regresses a parent component · case 05
The conflict resolution operation is admitted even though the resolved clock regresses a parent component.
Admit a conflict resolution result: Replicas execute different resolver versions · case 01
The conflict resolution operation is admitted even though replicas execute different resolver versions.
Admit a conflict resolution result: Replicas execute different resolver versions · case 02
The conflict resolution operation is admitted even though replicas execute different resolver versions.
Admit a conflict resolution result: Replicas execute different resolver versions · case 03
The conflict resolution operation is admitted even though replicas execute different resolver versions.
Admit a conflict resolution result: Replicas execute different resolver versions · case 04
The conflict resolution operation is admitted even though replicas execute different resolver versions.
Admit a conflict resolution result: Replicas execute different resolver versions · case 05
The conflict resolution operation is admitted even though replicas execute different resolver versions.
Admit a conflict resolution result: Resolution reuses an existing causal operation dot · case 01
The conflict resolution operation is admitted even though resolution reuses an existing causal operation dot.
Admit a conflict resolution result: Resolution reuses an existing causal operation dot · case 02
The conflict resolution operation is admitted even though resolution reuses an existing causal operation dot.
Admit a conflict resolution result: Resolution reuses an existing causal operation dot · case 03
The conflict resolution operation is admitted even though resolution reuses an existing causal operation dot.
Admit a conflict resolution result: Resolution reuses an existing causal operation dot · case 04
The conflict resolution operation is admitted even though resolution reuses an existing causal operation dot.
Admit a conflict resolution result: Resolution reuses an existing causal operation dot · case 05
The conflict resolution operation is admitted even though resolution reuses an existing causal operation dot.
Admit a conflict resolution result: A merge result violates the application value constraint · case 01
The conflict resolution operation is admitted even though a merge result violates the application value constraint.
Admit a conflict resolution result: A merge result violates the application value constraint · case 02
The conflict resolution operation is admitted even though a merge result violates the application value constraint.
Admit a conflict resolution result: A merge result violates the application value constraint · case 03
The conflict resolution operation is admitted even though a merge result violates the application value constraint.
Admit a conflict resolution result: A merge result violates the application value constraint · case 04
The conflict resolution operation is admitted even though a merge result violates the application value constraint.
Admit a conflict resolution result: A merge result violates the application value constraint · case 05
The conflict resolution operation is admitted even though a merge result violates the application value constraint.
Retire a replica and discard its data: Retirement leaves fewer copies than the required factor · case 01
The replica removal operation is admitted even though retirement leaves fewer copies than the required factor.
Retire a replica and discard its data: Retirement leaves fewer copies than the required factor · case 02
The replica removal operation is admitted even though retirement leaves fewer copies than the required factor.
Retire a replica and discard its data: Retirement leaves fewer copies than the required factor · case 03
The replica removal operation is admitted even though retirement leaves fewer copies than the required factor.
Retire a replica and discard its data: Retirement leaves fewer copies than the required factor · case 04
The replica removal operation is admitted even though retirement leaves fewer copies than the required factor.
Retire a replica and discard its data: Retirement leaves fewer copies than the required factor · case 05
The replica removal operation is admitted even though retirement leaves fewer copies than the required factor.
Retire a replica and discard its data: The replacement has only volatile copied state · case 01
The replica removal operation is admitted even though the replacement has only volatile copied state.
Retire a replica and discard its data: The replacement has only volatile copied state · case 02
The replica removal operation is admitted even though the replacement has only volatile copied state.
Retire a replica and discard its data: The replacement has only volatile copied state · case 03
The replica removal operation is admitted even though the replacement has only volatile copied state.
Retire a replica and discard its data: The replacement has only volatile copied state · case 04
The replica removal operation is admitted even though the replacement has only volatile copied state.
Retire a replica and discard its data: The replacement has only volatile copied state · case 05
The replica removal operation is admitted even though the replacement has only volatile copied state.
Retire a replica and discard its data: Keys still assigned to the retiring replica are lost · case 01
The replica removal operation is admitted even though keys still assigned to the retiring replica are lost.
Retire a replica and discard its data: Keys still assigned to the retiring replica are lost · case 02
The replica removal operation is admitted even though keys still assigned to the retiring replica are lost.
Retire a replica and discard its data: Keys still assigned to the retiring replica are lost · case 03
The replica removal operation is admitted even though keys still assigned to the retiring replica are lost.
Retire a replica and discard its data: Keys still assigned to the retiring replica are lost · case 04
The replica removal operation is admitted even though keys still assigned to the retiring replica are lost.
Retire a replica and discard its data: Keys still assigned to the retiring replica are lost · case 05
The replica removal operation is admitted even though keys still assigned to the retiring replica are lost.
Retire a replica and discard its data: Active snapshot readers lose their pinned source · case 01
The replica removal operation is admitted even though active snapshot readers lose their pinned source.
Retire a replica and discard its data: Active snapshot readers lose their pinned source · case 02
The replica removal operation is admitted even though active snapshot readers lose their pinned source.
Retire a replica and discard its data: Active snapshot readers lose their pinned source · case 03
The replica removal operation is admitted even though active snapshot readers lose their pinned source.
Retire a replica and discard its data: Active snapshot readers lose their pinned source · case 04
The replica removal operation is admitted even though active snapshot readers lose their pinned source.
Retire a replica and discard its data: Active snapshot readers lose their pinned source · case 05
The replica removal operation is admitted even though active snapshot readers lose their pinned source.
Retire a replica and discard its data: Physical removal precedes committed membership removal · case 01
The replica removal operation is admitted even though physical removal precedes committed membership removal.
Retire a replica and discard its data: Physical removal precedes committed membership removal · case 02
The replica removal operation is admitted even though physical removal precedes committed membership removal.
Retire a replica and discard its data: Physical removal precedes committed membership removal · case 03
The replica removal operation is admitted even though physical removal precedes committed membership removal.
Retire a replica and discard its data: Physical removal precedes committed membership removal · case 04
The replica removal operation is admitted even though physical removal precedes committed membership removal.
Retire a replica and discard its data: Physical removal precedes committed membership removal · case 05
The replica removal operation is admitted even though physical removal precedes committed membership removal.
Delete a write-ahead log segment: Deletion removes the next segment needed by a lagging replica · case 01
The wal retention operation is admitted even though deletion removes the next segment needed by a lagging replica.
Delete a write-ahead log segment: Deletion removes the next segment needed by a lagging replica · case 02
The wal retention operation is admitted even though deletion removes the next segment needed by a lagging replica.
Delete a write-ahead log segment: Deletion removes the next segment needed by a lagging replica · case 03
The wal retention operation is admitted even though deletion removes the next segment needed by a lagging replica.
Delete a write-ahead log segment: Deletion removes the next segment needed by a lagging replica · case 04
The wal retention operation is admitted even though deletion removes the next segment needed by a lagging replica.
Delete a write-ahead log segment: Deletion removes the next segment needed by a lagging replica · case 05
The wal retention operation is admitted even though deletion removes the next segment needed by a lagging replica.
Delete a write-ahead log segment: A backup still needs the selected log segment · case 01
The wal retention operation is admitted even though a backup still needs the selected log segment.
Delete a write-ahead log segment: A backup still needs the selected log segment · case 02
The wal retention operation is admitted even though a backup still needs the selected log segment.
Delete a write-ahead log segment: A backup still needs the selected log segment · case 03
The wal retention operation is admitted even though a backup still needs the selected log segment.
Delete a write-ahead log segment: A backup still needs the selected log segment · case 04
The wal retention operation is admitted even though a backup still needs the selected log segment.
Delete a write-ahead log segment: A backup still needs the selected log segment · case 05
The wal retention operation is admitted even though a backup still needs the selected log segment.
Delete a write-ahead log segment: The only recoverable copy is deleted before archival · case 01
The wal retention operation is admitted even though the only recoverable copy is deleted before archival.
Delete a write-ahead log segment: The only recoverable copy is deleted before archival · case 02
The wal retention operation is admitted even though the only recoverable copy is deleted before archival.
Delete a write-ahead log segment: The only recoverable copy is deleted before archival · case 03
The wal retention operation is admitted even though the only recoverable copy is deleted before archival.
Delete a write-ahead log segment: The only recoverable copy is deleted before archival · case 04
The wal retention operation is admitted even though the only recoverable copy is deleted before archival.
Delete a write-ahead log segment: The only recoverable copy is deleted before archival · case 05
The wal retention operation is admitted even though the only recoverable copy is deleted before archival.
Delete a write-ahead log segment: Garbage collection deletes a segment still accepting writes · case 01
The wal retention operation is admitted even though garbage collection deletes a segment still accepting writes.
Delete a write-ahead log segment: Garbage collection deletes a segment still accepting writes · case 02
The wal retention operation is admitted even though garbage collection deletes a segment still accepting writes.
Delete a write-ahead log segment: Garbage collection deletes a segment still accepting writes · case 03
The wal retention operation is admitted even though garbage collection deletes a segment still accepting writes.
Delete a write-ahead log segment: Garbage collection deletes a segment still accepting writes · case 04
The wal retention operation is admitted even though garbage collection deletes a segment still accepting writes.
Delete a write-ahead log segment: Garbage collection deletes a segment still accepting writes · case 05
The wal retention operation is admitted even though garbage collection deletes a segment still accepting writes.
Delete a write-ahead log segment: Deletion crosses the crash recovery replay floor · case 01
The wal retention operation is admitted even though deletion crosses the crash recovery replay floor.
Delete a write-ahead log segment: Deletion crosses the crash recovery replay floor · case 02
The wal retention operation is admitted even though deletion crosses the crash recovery replay floor.
Delete a write-ahead log segment: Deletion crosses the crash recovery replay floor · case 03
The wal retention operation is admitted even though deletion crosses the crash recovery replay floor.
Delete a write-ahead log segment: Deletion crosses the crash recovery replay floor · case 04
The wal retention operation is admitted even though deletion crosses the crash recovery replay floor.
Delete a write-ahead log segment: Deletion crosses the crash recovery replay floor · case 05
The wal retention operation is admitted even though deletion crosses the crash recovery replay floor.
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 ↗