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
Grouped notification interaction: uncached-expand from collapsed · case 01
The uncached-expand event leaves a notification in expanded instead of loading.
Grouped notification interaction: uncached-expand from collapsed · case 02
The uncached-expand event leaves a notification in expanded instead of loading.
Grouped notification interaction: uncached-expand from collapsed · case 03
The uncached-expand event leaves a notification in expanded instead of loading.
Grouped notification interaction: uncached-expand from collapsed · case 04
The uncached-expand event leaves a notification in expanded instead of loading.
Grouped notification interaction: uncached-expand from collapsed · case 05
The uncached-expand event leaves a notification in expanded instead of loading.
Grouped notification interaction: children-arrive from loading · case 01
The children-arrive event leaves a notification in collapsed instead of expanded.
Grouped notification interaction: children-arrive from loading · case 02
The children-arrive event leaves a notification in collapsed instead of expanded.
Grouped notification interaction: children-arrive from loading · case 03
The children-arrive event leaves a notification in collapsed instead of expanded.
Grouped notification interaction: children-arrive from loading · case 04
The children-arrive event leaves a notification in collapsed instead of expanded.
Grouped notification interaction: children-arrive from loading · case 05
The children-arrive event leaves a notification in collapsed instead of expanded.
Grouped notification interaction: children-fail from loading · case 01
The children-fail event leaves a notification in expanded instead of load-error.
Grouped notification interaction: children-fail from loading · case 02
The children-fail event leaves a notification in expanded instead of load-error.
Grouped notification interaction: children-fail from loading · case 03
The children-fail event leaves a notification in expanded instead of load-error.
Grouped notification interaction: children-fail from loading · case 04
The children-fail event leaves a notification in expanded instead of load-error.
Grouped notification interaction: children-fail from loading · case 05
The children-fail event leaves a notification in expanded instead of load-error.
Grouped notification interaction: retry-expand from load-error · case 01
The retry-expand event leaves a notification in expanded instead of loading.
Grouped notification interaction: retry-expand from load-error · case 02
The retry-expand event leaves a notification in expanded instead of loading.
Grouped notification interaction: retry-expand from load-error · case 03
The retry-expand event leaves a notification in expanded instead of loading.
Grouped notification interaction: retry-expand from load-error · case 04
The retry-expand event leaves a notification in expanded instead of loading.
Grouped notification interaction: retry-expand from load-error · case 05
The retry-expand event leaves a notification in expanded instead of loading.
Grouped notification interaction: collapse-during-load from loading · case 01
The collapse-during-load event leaves a notification in collapsed instead of collapse-pending.
Grouped notification interaction: collapse-during-load from loading · case 02
The collapse-during-load event leaves a notification in collapsed instead of collapse-pending.
Grouped notification interaction: collapse-during-load from loading · case 03
The collapse-during-load event leaves a notification in collapsed instead of collapse-pending.
Grouped notification interaction: collapse-during-load from loading · case 04
The collapse-during-load event leaves a notification in collapsed instead of collapse-pending.
Grouped notification interaction: collapse-during-load from loading · case 05
The collapse-during-load event leaves a notification in collapsed instead of collapse-pending.
Grouped notification interaction: children-arrive from collapse-pending · case 01
The children-arrive event leaves a notification in expanded instead of collapsed.
Grouped notification interaction: children-arrive from collapse-pending · case 02
The children-arrive event leaves a notification in expanded instead of collapsed.
Grouped notification interaction: children-arrive from collapse-pending · case 03
The children-arrive event leaves a notification in expanded instead of collapsed.
Grouped notification interaction: children-arrive from collapse-pending · case 04
The children-arrive event leaves a notification in expanded instead of collapsed.
Grouped notification interaction: children-arrive from collapse-pending · case 05
The children-arrive event leaves a notification in expanded instead of collapsed.
Grouped notification interaction: last-child-removed from expanded · case 01
The last-child-removed event leaves a notification in collapsed instead of empty.
Grouped notification interaction: last-child-removed from expanded · case 02
The last-child-removed event leaves a notification in collapsed instead of empty.
Grouped notification interaction: last-child-removed from expanded · case 03
The last-child-removed event leaves a notification in collapsed instead of empty.
Grouped notification interaction: last-child-removed from expanded · case 04
The last-child-removed event leaves a notification in collapsed instead of empty.
Grouped notification interaction: last-child-removed from expanded · case 05
The last-child-removed event leaves a notification in collapsed instead of empty.
Grouped notification interaction: first-child-added from empty · case 01
The first-child-added event leaves a notification in expanded instead of collapsed.
Grouped notification interaction: first-child-added from empty · case 02
The first-child-added event leaves a notification in expanded instead of collapsed.
Grouped notification interaction: first-child-added from empty · case 03
The first-child-added event leaves a notification in expanded instead of collapsed.
Grouped notification interaction: first-child-added from empty · case 04
The first-child-added event leaves a notification in expanded instead of collapsed.
Grouped notification interaction: first-child-added from empty · case 05
The first-child-added event leaves a notification in expanded instead of collapsed.
Visual notification delivery acknowledgement: mount-request from received · case 01
The mount-request event leaves a notification in seen instead of mounting.
Visual notification delivery acknowledgement: mount-request from received · case 02
The mount-request event leaves a notification in seen instead of mounting.
Visual notification delivery acknowledgement: mount-request from received · case 03
The mount-request event leaves a notification in seen instead of mounting.
Visual notification delivery acknowledgement: mount-request from received · case 04
The mount-request event leaves a notification in seen instead of mounting.
Visual notification delivery acknowledgement: mount-request from received · case 05
The mount-request event leaves a notification in seen instead of mounting.
Visual notification delivery acknowledgement: paint-confirmed from mounting · case 01
The paint-confirmed event leaves a notification in seen instead of ack-pending.
Visual notification delivery acknowledgement: paint-confirmed from mounting · case 02
The paint-confirmed event leaves a notification in seen instead of ack-pending.
Visual notification delivery acknowledgement: paint-confirmed from mounting · case 03
The paint-confirmed event leaves a notification in seen instead of ack-pending.
Visual notification delivery acknowledgement: paint-confirmed from mounting · case 04
The paint-confirmed event leaves a notification in seen instead of ack-pending.
Visual notification delivery acknowledgement: paint-confirmed from mounting · case 05
The paint-confirmed event leaves a notification in seen instead of ack-pending.
Visual notification delivery acknowledgement: mount-failed from mounting · case 01
The mount-failed event leaves a notification in seen instead of undisplayed.
Visual notification delivery acknowledgement: mount-failed from mounting · case 02
The mount-failed event leaves a notification in seen instead of undisplayed.
Visual notification delivery acknowledgement: mount-failed from mounting · case 03
The mount-failed event leaves a notification in seen instead of undisplayed.
Visual notification delivery acknowledgement: mount-failed from mounting · case 04
The mount-failed event leaves a notification in seen instead of undisplayed.
Visual notification delivery acknowledgement: mount-failed from mounting · case 05
The mount-failed event leaves a notification in seen instead of undisplayed.
Visual notification delivery acknowledgement: ack-success from ack-pending · case 01
The ack-success event leaves a notification in received instead of seen.
Visual notification delivery acknowledgement: ack-success from ack-pending · case 02
The ack-success event leaves a notification in received instead of seen.
Visual notification delivery acknowledgement: ack-success from ack-pending · case 03
The ack-success event leaves a notification in received instead of seen.
Visual notification delivery acknowledgement: ack-success from ack-pending · case 04
The ack-success event leaves a notification in received instead of seen.
Visual notification delivery acknowledgement: ack-success from ack-pending · case 05
The ack-success event leaves a notification in received instead of seen.
Visual notification delivery acknowledgement: ack-failure from ack-pending · case 01
The ack-failure event leaves a notification in seen instead of ack-retry.
Visual notification delivery acknowledgement: ack-failure from ack-pending · case 02
The ack-failure event leaves a notification in seen instead of ack-retry.
Visual notification delivery acknowledgement: ack-failure from ack-pending · case 03
The ack-failure event leaves a notification in seen instead of ack-retry.
Visual notification delivery acknowledgement: ack-failure from ack-pending · case 04
The ack-failure event leaves a notification in seen instead of ack-retry.
Visual notification delivery acknowledgement: ack-failure from ack-pending · case 05
The ack-failure event leaves a notification in seen instead of ack-retry.
Visual notification delivery acknowledgement: retry-ack from ack-retry · case 01
The retry-ack event leaves a notification in mounting instead of ack-pending.
Visual notification delivery acknowledgement: retry-ack from ack-retry · case 02
The retry-ack event leaves a notification in mounting instead of ack-pending.
Visual notification delivery acknowledgement: retry-ack from ack-retry · case 03
The retry-ack event leaves a notification in mounting instead of ack-pending.
Visual notification delivery acknowledgement: retry-ack from ack-retry · case 04
The retry-ack event leaves a notification in mounting instead of ack-pending.
Visual notification delivery acknowledgement: retry-ack from ack-retry · case 05
The retry-ack event leaves a notification in mounting instead of ack-pending.
Visual notification delivery acknowledgement: retry-mount from undisplayed · case 01
The retry-mount event leaves a notification in ack-pending instead of mounting.
Visual notification delivery acknowledgement: retry-mount from undisplayed · case 02
The retry-mount event leaves a notification in ack-pending instead of mounting.
Visual notification delivery acknowledgement: retry-mount from undisplayed · case 03
The retry-mount event leaves a notification in ack-pending instead of mounting.
Visual notification delivery acknowledgement: retry-mount from undisplayed · case 04
The retry-mount event leaves a notification in ack-pending instead of mounting.
Visual notification delivery acknowledgement: retry-mount from undisplayed · case 05
The retry-mount event leaves a notification in ack-pending instead of mounting.
Visual notification delivery acknowledgement: delivery-replay from seen · case 01
The delivery-replay event leaves a notification in mounting instead of seen.
Visual notification delivery acknowledgement: delivery-replay from seen · case 02
The delivery-replay event leaves a notification in mounting instead of seen.
Visual notification delivery acknowledgement: delivery-replay from seen · case 03
The delivery-replay event leaves a notification in mounting instead of seen.
Visual notification delivery acknowledgement: delivery-replay from seen · case 04
The delivery-replay event leaves a notification in mounting instead of seen.
Visual notification delivery acknowledgement: delivery-replay from seen · case 05
The delivery-replay event leaves a notification in mounting instead of seen.
Visual notification delivery acknowledgement: route-unmount from mounting · case 01
The route-unmount event leaves a notification in seen instead of undisplayed.
Visual notification delivery acknowledgement: route-unmount from mounting · case 02
The route-unmount event leaves a notification in seen instead of undisplayed.
Visual notification delivery acknowledgement: route-unmount from mounting · case 03
The route-unmount event leaves a notification in seen instead of undisplayed.
Visual notification delivery acknowledgement: route-unmount from mounting · case 04
The route-unmount event leaves a notification in seen instead of undisplayed.
Visual notification delivery acknowledgement: route-unmount from mounting · case 05
The route-unmount event leaves a notification in seen instead of undisplayed.
Visual notification delivery acknowledgement: surface-unmount from ack-retry · case 01
The surface-unmount event leaves a notification in received instead of ack-retry.
Visual notification delivery acknowledgement: surface-unmount from ack-retry · case 02
The surface-unmount event leaves a notification in received instead of ack-retry.
Visual notification delivery acknowledgement: surface-unmount from ack-retry · case 03
The surface-unmount event leaves a notification in received instead of ack-retry.
Visual notification delivery acknowledgement: surface-unmount from ack-retry · case 04
The surface-unmount event leaves a notification in received instead of ack-retry.
Visual notification delivery acknowledgement: surface-unmount from ack-retry · case 05
The surface-unmount event leaves a notification in received instead of ack-retry.
Notification inbox reconnect recovery: connection-lost from live · case 01
The connection-lost event leaves a notification in empty instead of offline-cached.
Notification inbox reconnect recovery: connection-lost from live · case 02
The connection-lost event leaves a notification in empty instead of offline-cached.
Notification inbox reconnect recovery: connection-lost from live · case 03
The connection-lost event leaves a notification in empty instead of offline-cached.
Notification inbox reconnect recovery: connection-lost from live · case 04
The connection-lost event leaves a notification in empty instead of offline-cached.
Notification inbox reconnect recovery: connection-lost from live · case 05
The connection-lost event leaves a notification in empty instead of offline-cached.
Notification inbox reconnect recovery: connection-restored from offline-cached · case 01
The connection-restored event leaves a notification in live instead of reconciling.
Notification inbox reconnect recovery: connection-restored from offline-cached · case 02
The connection-restored event leaves a notification in live instead of reconciling.
Notification inbox reconnect recovery: connection-restored from offline-cached · case 03
The connection-restored event leaves a notification in live instead of reconciling.
Notification inbox reconnect recovery: connection-restored from offline-cached · case 04
The connection-restored event leaves a notification in live instead of reconciling.
Notification inbox reconnect recovery: connection-restored from offline-cached · case 05
The connection-restored event leaves a notification in live instead of reconciling.
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 ↗