FAILURE MAP

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 ↗
100840Executable case variants
20168Distinct failure mechanisms
302520Executed implementations
20168Open-access cases

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

Python · Standard library
REFERENCEFAILURE MECHANISMDOMAINACCESS
FA-34501

Swipe-to-dismiss notification feedback: above-threshold-release from dragging · case 01

The above-threshold-release event leaves a notification in dismissed instead of committing.

Notification interfaces● Open access↗
FA-34502

Swipe-to-dismiss notification feedback: above-threshold-release from dragging · case 02

The above-threshold-release event leaves a notification in dismissed instead of committing.

Notification interfaces◈ Members↗
FA-34503

Swipe-to-dismiss notification feedback: above-threshold-release from dragging · case 03

The above-threshold-release event leaves a notification in dismissed instead of committing.

Notification interfaces◈ Members↗
FA-34504

Swipe-to-dismiss notification feedback: above-threshold-release from dragging · case 04

The above-threshold-release event leaves a notification in dismissed instead of committing.

Notification interfaces◈ Members↗
FA-34505

Swipe-to-dismiss notification feedback: above-threshold-release from dragging · case 05

The above-threshold-release event leaves a notification in dismissed instead of committing.

Notification interfaces◈ Members↗
FA-34506

Swipe-to-dismiss notification feedback: snapback-finished from returning · case 01

The snapback-finished event leaves a notification in dismissed instead of resting.

Notification interfaces● Open access↗
FA-34507

Swipe-to-dismiss notification feedback: snapback-finished from returning · case 02

The snapback-finished event leaves a notification in dismissed instead of resting.

Notification interfaces◈ Members↗
FA-34508

Swipe-to-dismiss notification feedback: snapback-finished from returning · case 03

The snapback-finished event leaves a notification in dismissed instead of resting.

Notification interfaces◈ Members↗
FA-34509

Swipe-to-dismiss notification feedback: snapback-finished from returning · case 04

The snapback-finished event leaves a notification in dismissed instead of resting.

Notification interfaces◈ Members↗
FA-34510

Swipe-to-dismiss notification feedback: snapback-finished from returning · case 05

The snapback-finished event leaves a notification in dismissed instead of resting.

Notification interfaces◈ Members↗
FA-34511

Swipe-to-dismiss notification feedback: dismiss-accepted from committing · case 01

The dismiss-accepted event leaves a notification in resting instead of exit-animating.

Notification interfaces● Open access↗
FA-34512

Swipe-to-dismiss notification feedback: dismiss-accepted from committing · case 02

The dismiss-accepted event leaves a notification in resting instead of exit-animating.

Notification interfaces◈ Members↗
FA-34513

Swipe-to-dismiss notification feedback: dismiss-accepted from committing · case 03

The dismiss-accepted event leaves a notification in resting instead of exit-animating.

Notification interfaces◈ Members↗
FA-34514

Swipe-to-dismiss notification feedback: dismiss-accepted from committing · case 04

The dismiss-accepted event leaves a notification in resting instead of exit-animating.

Notification interfaces◈ Members↗
FA-34515

Swipe-to-dismiss notification feedback: dismiss-accepted from committing · case 05

The dismiss-accepted event leaves a notification in resting instead of exit-animating.

Notification interfaces◈ Members↗
FA-34516

Swipe-to-dismiss notification feedback: dismiss-rejected from committing · case 01

The dismiss-rejected event leaves a notification in dismissed instead of returning.

Notification interfaces● Open access↗
FA-34517

Swipe-to-dismiss notification feedback: dismiss-rejected from committing · case 02

The dismiss-rejected event leaves a notification in dismissed instead of returning.

Notification interfaces◈ Members↗
FA-34518

Swipe-to-dismiss notification feedback: dismiss-rejected from committing · case 03

The dismiss-rejected event leaves a notification in dismissed instead of returning.

Notification interfaces◈ Members↗
FA-34519

Swipe-to-dismiss notification feedback: dismiss-rejected from committing · case 04

The dismiss-rejected event leaves a notification in dismissed instead of returning.

Notification interfaces◈ Members↗
FA-34520

Swipe-to-dismiss notification feedback: dismiss-rejected from committing · case 05

The dismiss-rejected event leaves a notification in dismissed instead of returning.

Notification interfaces◈ Members↗
FA-34521

Swipe-to-dismiss notification feedback: animation-finished from exit-animating · case 01

The animation-finished event leaves a notification in resting instead of dismissed.

Notification interfaces● Open access↗
FA-34522

Swipe-to-dismiss notification feedback: animation-finished from exit-animating · case 02

The animation-finished event leaves a notification in resting instead of dismissed.

Notification interfaces◈ Members↗
FA-34523

Swipe-to-dismiss notification feedback: animation-finished from exit-animating · case 03

The animation-finished event leaves a notification in resting instead of dismissed.

Notification interfaces◈ Members↗
FA-34524

Swipe-to-dismiss notification feedback: animation-finished from exit-animating · case 04

The animation-finished event leaves a notification in resting instead of dismissed.

Notification interfaces◈ Members↗
FA-34525

Swipe-to-dismiss notification feedback: animation-finished from exit-animating · case 05

The animation-finished event leaves a notification in resting instead of dismissed.

Notification interfaces◈ Members↗
FA-34526

Swipe-to-dismiss notification feedback: pointer-cancel from dragging · case 01

The pointer-cancel event leaves a notification in committing instead of returning.

Notification interfaces● Open access↗
FA-34527

Swipe-to-dismiss notification feedback: pointer-cancel from dragging · case 02

The pointer-cancel event leaves a notification in committing instead of returning.

Notification interfaces◈ Members↗
FA-34528

Swipe-to-dismiss notification feedback: pointer-cancel from dragging · case 03

The pointer-cancel event leaves a notification in committing instead of returning.

Notification interfaces◈ Members↗
FA-34529

Swipe-to-dismiss notification feedback: pointer-cancel from dragging · case 04

The pointer-cancel event leaves a notification in committing instead of returning.

Notification interfaces◈ Members↗
FA-34530

Swipe-to-dismiss notification feedback: pointer-cancel from dragging · case 05

The pointer-cancel event leaves a notification in committing instead of returning.

Notification interfaces◈ Members↗
FA-34531

Swipe-to-dismiss notification feedback: reduced-motion-enabled from exit-animating · case 01

The reduced-motion-enabled event leaves a notification in resting instead of dismissed.

Notification interfaces● Open access↗
FA-34532

Swipe-to-dismiss notification feedback: reduced-motion-enabled from exit-animating · case 02

The reduced-motion-enabled event leaves a notification in resting instead of dismissed.

Notification interfaces◈ Members↗
FA-34533

Swipe-to-dismiss notification feedback: reduced-motion-enabled from exit-animating · case 03

The reduced-motion-enabled event leaves a notification in resting instead of dismissed.

Notification interfaces◈ Members↗
FA-34534

Swipe-to-dismiss notification feedback: reduced-motion-enabled from exit-animating · case 04

The reduced-motion-enabled event leaves a notification in resting instead of dismissed.

Notification interfaces◈ Members↗
FA-34535

Swipe-to-dismiss notification feedback: reduced-motion-enabled from exit-animating · case 05

The reduced-motion-enabled event leaves a notification in resting instead of dismissed.

Notification interfaces◈ Members↗
FA-34536

Swipe-to-dismiss notification feedback: second-pointer-down from committing · case 01

The second-pointer-down event leaves a notification in dragging instead of committing.

Notification interfaces● Open access↗
FA-34537

Swipe-to-dismiss notification feedback: second-pointer-down from committing · case 02

The second-pointer-down event leaves a notification in dragging instead of committing.

Notification interfaces◈ Members↗
FA-34538

Swipe-to-dismiss notification feedback: second-pointer-down from committing · case 03

The second-pointer-down event leaves a notification in dragging instead of committing.

Notification interfaces◈ Members↗
FA-34539

Swipe-to-dismiss notification feedback: second-pointer-down from committing · case 04

The second-pointer-down event leaves a notification in dragging instead of committing.

Notification interfaces◈ Members↗
FA-34540

Swipe-to-dismiss notification feedback: second-pointer-down from committing · case 05

The second-pointer-down event leaves a notification in dragging instead of committing.

Notification interfaces◈ Members↗
FA-34541

Notification inbox initial restoration: cache-found from placeholder · case 01

The cache-found event leaves a notification in ready instead of cached-unverified.

Notification interfaces● Open access↗
FA-34542

Notification inbox initial restoration: cache-found from placeholder · case 02

The cache-found event leaves a notification in ready instead of cached-unverified.

Notification interfaces◈ Members↗
FA-34543

Notification inbox initial restoration: cache-found from placeholder · case 03

The cache-found event leaves a notification in ready instead of cached-unverified.

Notification interfaces◈ Members↗
FA-34544

Notification inbox initial restoration: cache-found from placeholder · case 04

The cache-found event leaves a notification in ready instead of cached-unverified.

Notification interfaces◈ Members↗
FA-34545

Notification inbox initial restoration: cache-found from placeholder · case 05

The cache-found event leaves a notification in ready instead of cached-unverified.

Notification interfaces◈ Members↗
FA-34546

Notification inbox initial restoration: cache-missing from placeholder · case 01

The cache-missing event leaves a notification in empty instead of fetching.

Notification interfaces● Open access↗
FA-34547

Notification inbox initial restoration: cache-missing from placeholder · case 02

The cache-missing event leaves a notification in empty instead of fetching.

Notification interfaces◈ Members↗
FA-34548

Notification inbox initial restoration: cache-missing from placeholder · case 03

The cache-missing event leaves a notification in empty instead of fetching.

Notification interfaces◈ Members↗
FA-34549

Notification inbox initial restoration: cache-missing from placeholder · case 04

The cache-missing event leaves a notification in empty instead of fetching.

Notification interfaces◈ Members↗
FA-34550

Notification inbox initial restoration: cache-missing from placeholder · case 05

The cache-missing event leaves a notification in empty instead of fetching.

Notification interfaces◈ Members↗
FA-34551

Notification inbox initial restoration: refresh-start from cached-unverified · case 01

The refresh-start event leaves a notification in placeholder instead of refreshing-cache.

Notification interfaces● Open access↗
FA-34552

Notification inbox initial restoration: refresh-start from cached-unverified · case 02

The refresh-start event leaves a notification in placeholder instead of refreshing-cache.

Notification interfaces◈ Members↗
FA-34553

Notification inbox initial restoration: refresh-start from cached-unverified · case 03

The refresh-start event leaves a notification in placeholder instead of refreshing-cache.

Notification interfaces◈ Members↗
FA-34554

Notification inbox initial restoration: refresh-start from cached-unverified · case 04

The refresh-start event leaves a notification in placeholder instead of refreshing-cache.

Notification interfaces◈ Members↗
FA-34555

Notification inbox initial restoration: refresh-start from cached-unverified · case 05

The refresh-start event leaves a notification in placeholder instead of refreshing-cache.

Notification interfaces◈ Members↗
FA-34556

Notification inbox initial restoration: fresh-nonempty from refreshing-cache · case 01

The fresh-nonempty event leaves a notification in empty instead of ready.

Notification interfaces● Open access↗
FA-34557

Notification inbox initial restoration: fresh-nonempty from refreshing-cache · case 02

The fresh-nonempty event leaves a notification in empty instead of ready.

Notification interfaces◈ Members↗
FA-34558

Notification inbox initial restoration: fresh-nonempty from refreshing-cache · case 03

The fresh-nonempty event leaves a notification in empty instead of ready.

Notification interfaces◈ Members↗
FA-34559

Notification inbox initial restoration: fresh-nonempty from refreshing-cache · case 04

The fresh-nonempty event leaves a notification in empty instead of ready.

Notification interfaces◈ Members↗
FA-34560

Notification inbox initial restoration: fresh-nonempty from refreshing-cache · case 05

The fresh-nonempty event leaves a notification in empty instead of ready.

Notification interfaces◈ Members↗
FA-34561

Notification inbox initial restoration: fresh-empty from refreshing-cache · case 01

The fresh-empty event leaves a notification in ready instead of empty.

Notification interfaces● Open access↗
FA-34562

Notification inbox initial restoration: fresh-empty from refreshing-cache · case 02

The fresh-empty event leaves a notification in ready instead of empty.

Notification interfaces◈ Members↗
FA-34563

Notification inbox initial restoration: fresh-empty from refreshing-cache · case 03

The fresh-empty event leaves a notification in ready instead of empty.

Notification interfaces◈ Members↗
FA-34564

Notification inbox initial restoration: fresh-empty from refreshing-cache · case 04

The fresh-empty event leaves a notification in ready instead of empty.

Notification interfaces◈ Members↗
FA-34565

Notification inbox initial restoration: fresh-empty from refreshing-cache · case 05

The fresh-empty event leaves a notification in ready instead of empty.

Notification interfaces◈ Members↗
FA-34566

Notification inbox initial restoration: refresh-error from refreshing-cache · case 01

The refresh-error event leaves a notification in empty instead of stale-warning.

Notification interfaces● Open access↗
FA-34567

Notification inbox initial restoration: refresh-error from refreshing-cache · case 02

The refresh-error event leaves a notification in empty instead of stale-warning.

Notification interfaces◈ Members↗
FA-34568

Notification inbox initial restoration: refresh-error from refreshing-cache · case 03

The refresh-error event leaves a notification in empty instead of stale-warning.

Notification interfaces◈ Members↗
FA-34569

Notification inbox initial restoration: refresh-error from refreshing-cache · case 04

The refresh-error event leaves a notification in empty instead of stale-warning.

Notification interfaces◈ Members↗
FA-34570

Notification inbox initial restoration: refresh-error from refreshing-cache · case 05

The refresh-error event leaves a notification in empty instead of stale-warning.

Notification interfaces◈ Members↗
FA-34571

Notification inbox initial restoration: fresh-nonempty from fetching · case 01

The fresh-nonempty event leaves a notification in empty instead of ready.

Notification interfaces● Open access↗
FA-34572

Notification inbox initial restoration: fresh-nonempty from fetching · case 02

The fresh-nonempty event leaves a notification in empty instead of ready.

Notification interfaces◈ Members↗
FA-34573

Notification inbox initial restoration: fresh-nonempty from fetching · case 03

The fresh-nonempty event leaves a notification in empty instead of ready.

Notification interfaces◈ Members↗
FA-34574

Notification inbox initial restoration: fresh-nonempty from fetching · case 04

The fresh-nonempty event leaves a notification in empty instead of ready.

Notification interfaces◈ Members↗
FA-34575

Notification inbox initial restoration: fresh-nonempty from fetching · case 05

The fresh-nonempty event leaves a notification in empty instead of ready.

Notification interfaces◈ Members↗
FA-34576

Notification inbox initial restoration: fresh-empty from fetching · case 01

The fresh-empty event leaves a notification in ready instead of empty.

Notification interfaces● Open access↗
FA-34577

Notification inbox initial restoration: fresh-empty from fetching · case 02

The fresh-empty event leaves a notification in ready instead of empty.

Notification interfaces◈ Members↗
FA-34578

Notification inbox initial restoration: fresh-empty from fetching · case 03

The fresh-empty event leaves a notification in ready instead of empty.

Notification interfaces◈ Members↗
FA-34579

Notification inbox initial restoration: fresh-empty from fetching · case 04

The fresh-empty event leaves a notification in ready instead of empty.

Notification interfaces◈ Members↗
FA-34580

Notification inbox initial restoration: fresh-empty from fetching · case 05

The fresh-empty event leaves a notification in ready instead of empty.

Notification interfaces◈ Members↗
FA-34581

Notification inbox initial restoration: refresh-error from fetching · case 01

The refresh-error event leaves a notification in empty instead of load-error.

Notification interfaces● Open access↗
FA-34582

Notification inbox initial restoration: refresh-error from fetching · case 02

The refresh-error event leaves a notification in empty instead of load-error.

Notification interfaces◈ Members↗
FA-34583

Notification inbox initial restoration: refresh-error from fetching · case 03

The refresh-error event leaves a notification in empty instead of load-error.

Notification interfaces◈ Members↗
FA-34584

Notification inbox initial restoration: refresh-error from fetching · case 04

The refresh-error event leaves a notification in empty instead of load-error.

Notification interfaces◈ Members↗
FA-34585

Notification inbox initial restoration: refresh-error from fetching · case 05

The refresh-error event leaves a notification in empty instead of load-error.

Notification interfaces◈ Members↗
FA-34586

Notification inbox initial restoration: retry-refresh from stale-warning · case 01

The retry-refresh event leaves a notification in placeholder instead of refreshing-cache.

Notification interfaces● Open access↗
FA-34587

Notification inbox initial restoration: retry-refresh from stale-warning · case 02

The retry-refresh event leaves a notification in placeholder instead of refreshing-cache.

Notification interfaces◈ Members↗
FA-34588

Notification inbox initial restoration: retry-refresh from stale-warning · case 03

The retry-refresh event leaves a notification in placeholder instead of refreshing-cache.

Notification interfaces◈ Members↗
FA-34589

Notification inbox initial restoration: retry-refresh from stale-warning · case 04

The retry-refresh event leaves a notification in placeholder instead of refreshing-cache.

Notification interfaces◈ Members↗
FA-34590

Notification inbox initial restoration: retry-refresh from stale-warning · case 05

The retry-refresh event leaves a notification in placeholder instead of refreshing-cache.

Notification interfaces◈ Members↗
FA-34591

Inbox optimistic archive rollback: archive-click from row-visible · case 01

The archive-click event leaves a notification in archived instead of optimistically-hidden.

Notification interfaces● Open access↗
FA-34592

Inbox optimistic archive rollback: archive-click from row-visible · case 02

The archive-click event leaves a notification in archived instead of optimistically-hidden.

Notification interfaces◈ Members↗
FA-34593

Inbox optimistic archive rollback: archive-click from row-visible · case 03

The archive-click event leaves a notification in archived instead of optimistically-hidden.

Notification interfaces◈ Members↗
FA-34594

Inbox optimistic archive rollback: archive-click from row-visible · case 04

The archive-click event leaves a notification in archived instead of optimistically-hidden.

Notification interfaces◈ Members↗
FA-34595

Inbox optimistic archive rollback: archive-click from row-visible · case 05

The archive-click event leaves a notification in archived instead of optimistically-hidden.

Notification interfaces◈ Members↗
FA-34596

Inbox optimistic archive rollback: archive-success from optimistically-hidden · case 01

The archive-success event leaves a notification in row-visible instead of archived.

Notification interfaces● Open access↗
FA-34597

Inbox optimistic archive rollback: archive-success from optimistically-hidden · case 02

The archive-success event leaves a notification in row-visible instead of archived.

Notification interfaces◈ Members↗
FA-34598

Inbox optimistic archive rollback: archive-success from optimistically-hidden · case 03

The archive-success event leaves a notification in row-visible instead of archived.

Notification interfaces◈ Members↗
FA-34599

Inbox optimistic archive rollback: archive-success from optimistically-hidden · case 04

The archive-success event leaves a notification in row-visible instead of archived.

Notification interfaces◈ Members↗
FA-34600

Inbox optimistic archive rollback: archive-success from optimistically-hidden · case 05

The archive-success event leaves a notification in row-visible instead of archived.

Notification interfaces◈ Members↗

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 ↗