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-34801

Inbox notification pin persistence: pin-failure from pin-pending · case 01

The pin-failure event leaves a notification in pinned instead of pin-error.

Notification interfaces● Open access↗
FA-34802

Inbox notification pin persistence: pin-failure from pin-pending · case 02

The pin-failure event leaves a notification in pinned instead of pin-error.

Notification interfaces◈ Members↗
FA-34803

Inbox notification pin persistence: pin-failure from pin-pending · case 03

The pin-failure event leaves a notification in pinned instead of pin-error.

Notification interfaces◈ Members↗
FA-34804

Inbox notification pin persistence: pin-failure from pin-pending · case 04

The pin-failure event leaves a notification in pinned instead of pin-error.

Notification interfaces◈ Members↗
FA-34805

Inbox notification pin persistence: pin-failure from pin-pending · case 05

The pin-failure event leaves a notification in pinned instead of pin-error.

Notification interfaces◈ Members↗
FA-34806

Inbox notification pin persistence: unpin-click from pinned · case 01

The unpin-click event leaves a notification in unpinned instead of unpin-pending.

Notification interfaces● Open access↗
FA-34807

Inbox notification pin persistence: unpin-click from pinned · case 02

The unpin-click event leaves a notification in unpinned instead of unpin-pending.

Notification interfaces◈ Members↗
FA-34808

Inbox notification pin persistence: unpin-click from pinned · case 03

The unpin-click event leaves a notification in unpinned instead of unpin-pending.

Notification interfaces◈ Members↗
FA-34809

Inbox notification pin persistence: unpin-click from pinned · case 04

The unpin-click event leaves a notification in unpinned instead of unpin-pending.

Notification interfaces◈ Members↗
FA-34810

Inbox notification pin persistence: unpin-click from pinned · case 05

The unpin-click event leaves a notification in unpinned instead of unpin-pending.

Notification interfaces◈ Members↗
FA-34811

Inbox notification pin persistence: unpin-success from unpin-pending · case 01

The unpin-success event leaves a notification in pinned instead of unpinned.

Notification interfaces● Open access↗
FA-34812

Inbox notification pin persistence: unpin-success from unpin-pending · case 02

The unpin-success event leaves a notification in pinned instead of unpinned.

Notification interfaces◈ Members↗
FA-34813

Inbox notification pin persistence: unpin-success from unpin-pending · case 03

The unpin-success event leaves a notification in pinned instead of unpinned.

Notification interfaces◈ Members↗
FA-34814

Inbox notification pin persistence: unpin-success from unpin-pending · case 04

The unpin-success event leaves a notification in pinned instead of unpinned.

Notification interfaces◈ Members↗
FA-34815

Inbox notification pin persistence: unpin-success from unpin-pending · case 05

The unpin-success event leaves a notification in pinned instead of unpinned.

Notification interfaces◈ Members↗
FA-34816

Inbox notification pin persistence: unpin-failure from unpin-pending · case 01

The unpin-failure event leaves a notification in unpinned instead of unpin-error.

Notification interfaces● Open access↗
FA-34817

Inbox notification pin persistence: unpin-failure from unpin-pending · case 02

The unpin-failure event leaves a notification in unpinned instead of unpin-error.

Notification interfaces◈ Members↗
FA-34818

Inbox notification pin persistence: unpin-failure from unpin-pending · case 03

The unpin-failure event leaves a notification in unpinned instead of unpin-error.

Notification interfaces◈ Members↗
FA-34819

Inbox notification pin persistence: unpin-failure from unpin-pending · case 04

The unpin-failure event leaves a notification in unpinned instead of unpin-error.

Notification interfaces◈ Members↗
FA-34820

Inbox notification pin persistence: unpin-failure from unpin-pending · case 05

The unpin-failure event leaves a notification in unpinned instead of unpin-error.

Notification interfaces◈ Members↗
FA-34821

Inbox notification pin persistence: cancel-pin-intent from pin-error · case 01

The cancel-pin-intent event leaves a notification in pinned instead of unpinned.

Notification interfaces● Open access↗
FA-34822

Inbox notification pin persistence: cancel-pin-intent from pin-error · case 02

The cancel-pin-intent event leaves a notification in pinned instead of unpinned.

Notification interfaces◈ Members↗
FA-34823

Inbox notification pin persistence: cancel-pin-intent from pin-error · case 03

The cancel-pin-intent event leaves a notification in pinned instead of unpinned.

Notification interfaces◈ Members↗
FA-34824

Inbox notification pin persistence: cancel-pin-intent from pin-error · case 04

The cancel-pin-intent event leaves a notification in pinned instead of unpinned.

Notification interfaces◈ Members↗
FA-34825

Inbox notification pin persistence: cancel-pin-intent from pin-error · case 05

The cancel-pin-intent event leaves a notification in pinned instead of unpinned.

Notification interfaces◈ Members↗
FA-34826

Inbox notification pin persistence: cancel-unpin-intent from unpin-error · case 01

The cancel-unpin-intent event leaves a notification in unpinned instead of pinned.

Notification interfaces● Open access↗
FA-34827

Inbox notification pin persistence: cancel-unpin-intent from unpin-error · case 02

The cancel-unpin-intent event leaves a notification in unpinned instead of pinned.

Notification interfaces◈ Members↗
FA-34828

Inbox notification pin persistence: cancel-unpin-intent from unpin-error · case 03

The cancel-unpin-intent event leaves a notification in unpinned instead of pinned.

Notification interfaces◈ Members↗
FA-34829

Inbox notification pin persistence: cancel-unpin-intent from unpin-error · case 04

The cancel-unpin-intent event leaves a notification in unpinned instead of pinned.

Notification interfaces◈ Members↗
FA-34830

Inbox notification pin persistence: cancel-unpin-intent from unpin-error · case 05

The cancel-unpin-intent event leaves a notification in unpinned instead of pinned.

Notification interfaces◈ Members↗
FA-34831

Inbox notification pin persistence: notification-expires from pinned · case 01

The notification-expires event leaves a notification in unpinned instead of expired-pinned.

Notification interfaces● Open access↗
FA-34832

Inbox notification pin persistence: notification-expires from pinned · case 02

The notification-expires event leaves a notification in unpinned instead of expired-pinned.

Notification interfaces◈ Members↗
FA-34833

Inbox notification pin persistence: notification-expires from pinned · case 03

The notification-expires event leaves a notification in unpinned instead of expired-pinned.

Notification interfaces◈ Members↗
FA-34834

Inbox notification pin persistence: notification-expires from pinned · case 04

The notification-expires event leaves a notification in unpinned instead of expired-pinned.

Notification interfaces◈ Members↗
FA-34835

Inbox notification pin persistence: notification-expires from pinned · case 05

The notification-expires event leaves a notification in unpinned instead of expired-pinned.

Notification interfaces◈ Members↗
FA-34836

Inbox notification pin persistence: unpin-expired from expired-pinned · case 01

The unpin-expired event leaves a notification in pinned instead of gone.

Notification interfaces● Open access↗
FA-34837

Inbox notification pin persistence: unpin-expired from expired-pinned · case 02

The unpin-expired event leaves a notification in pinned instead of gone.

Notification interfaces◈ Members↗
FA-34838

Inbox notification pin persistence: unpin-expired from expired-pinned · case 03

The unpin-expired event leaves a notification in pinned instead of gone.

Notification interfaces◈ Members↗
FA-34839

Inbox notification pin persistence: unpin-expired from expired-pinned · case 04

The unpin-expired event leaves a notification in pinned instead of gone.

Notification interfaces◈ Members↗
FA-34840

Inbox notification pin persistence: unpin-expired from expired-pinned · case 05

The unpin-expired event leaves a notification in pinned instead of gone.

Notification interfaces◈ Members↗
FA-34841

Inbox history pagination presentation: load-older from first-page · case 01

The load-older event leaves a notification in end-of-history instead of loading-older.

Notification interfaces● Open access↗
FA-34842

Inbox history pagination presentation: load-older from first-page · case 02

The load-older event leaves a notification in end-of-history instead of loading-older.

Notification interfaces◈ Members↗
FA-34843

Inbox history pagination presentation: load-older from first-page · case 03

The load-older event leaves a notification in end-of-history instead of loading-older.

Notification interfaces◈ Members↗
FA-34844

Inbox history pagination presentation: load-older from first-page · case 04

The load-older event leaves a notification in end-of-history instead of loading-older.

Notification interfaces◈ Members↗
FA-34845

Inbox history pagination presentation: load-older from first-page · case 05

The load-older event leaves a notification in end-of-history instead of loading-older.

Notification interfaces◈ Members↗
FA-34846

Inbox history pagination presentation: nonempty-page from loading-older · case 01

The nonempty-page event leaves a notification in first-page instead of older-appended.

Notification interfaces● Open access↗
FA-34847

Inbox history pagination presentation: nonempty-page from loading-older · case 02

The nonempty-page event leaves a notification in first-page instead of older-appended.

Notification interfaces◈ Members↗
FA-34848

Inbox history pagination presentation: nonempty-page from loading-older · case 03

The nonempty-page event leaves a notification in first-page instead of older-appended.

Notification interfaces◈ Members↗
FA-34849

Inbox history pagination presentation: nonempty-page from loading-older · case 04

The nonempty-page event leaves a notification in first-page instead of older-appended.

Notification interfaces◈ Members↗
FA-34850

Inbox history pagination presentation: nonempty-page from loading-older · case 05

The nonempty-page event leaves a notification in first-page instead of older-appended.

Notification interfaces◈ Members↗
FA-34851

Inbox history pagination presentation: empty-page from loading-older · case 01

The empty-page event leaves a notification in older-appended instead of end-of-history.

Notification interfaces● Open access↗
FA-34852

Inbox history pagination presentation: empty-page from loading-older · case 02

The empty-page event leaves a notification in older-appended instead of end-of-history.

Notification interfaces◈ Members↗
FA-34853

Inbox history pagination presentation: empty-page from loading-older · case 03

The empty-page event leaves a notification in older-appended instead of end-of-history.

Notification interfaces◈ Members↗
FA-34854

Inbox history pagination presentation: empty-page from loading-older · case 04

The empty-page event leaves a notification in older-appended instead of end-of-history.

Notification interfaces◈ Members↗
FA-34855

Inbox history pagination presentation: empty-page from loading-older · case 05

The empty-page event leaves a notification in older-appended instead of end-of-history.

Notification interfaces◈ Members↗
FA-34856

Inbox history pagination presentation: page-failure from loading-older · case 01

The page-failure event leaves a notification in end-of-history instead of older-error.

Notification interfaces● Open access↗
FA-34857

Inbox history pagination presentation: page-failure from loading-older · case 02

The page-failure event leaves a notification in end-of-history instead of older-error.

Notification interfaces◈ Members↗
FA-34858

Inbox history pagination presentation: page-failure from loading-older · case 03

The page-failure event leaves a notification in end-of-history instead of older-error.

Notification interfaces◈ Members↗
FA-34859

Inbox history pagination presentation: page-failure from loading-older · case 04

The page-failure event leaves a notification in end-of-history instead of older-error.

Notification interfaces◈ Members↗
FA-34860

Inbox history pagination presentation: page-failure from loading-older · case 05

The page-failure event leaves a notification in end-of-history instead of older-error.

Notification interfaces◈ Members↗
FA-34861

Inbox history pagination presentation: retry-older from older-error · case 01

The retry-older event leaves a notification in end-of-history instead of loading-older.

Notification interfaces● Open access↗
FA-34862

Inbox history pagination presentation: retry-older from older-error · case 02

The retry-older event leaves a notification in end-of-history instead of loading-older.

Notification interfaces◈ Members↗
FA-34863

Inbox history pagination presentation: retry-older from older-error · case 03

The retry-older event leaves a notification in end-of-history instead of loading-older.

Notification interfaces◈ Members↗
FA-34864

Inbox history pagination presentation: retry-older from older-error · case 04

The retry-older event leaves a notification in end-of-history instead of loading-older.

Notification interfaces◈ Members↗
FA-34865

Inbox history pagination presentation: retry-older from older-error · case 05

The retry-older event leaves a notification in end-of-history instead of loading-older.

Notification interfaces◈ Members↗
FA-34866

Inbox history pagination presentation: new-head-arrives from older-appended · case 01

The new-head-arrives event leaves a notification in first-page instead of head-update-pending.

Notification interfaces● Open access↗
FA-34867

Inbox history pagination presentation: new-head-arrives from older-appended · case 02

The new-head-arrives event leaves a notification in first-page instead of head-update-pending.

Notification interfaces◈ Members↗
FA-34868

Inbox history pagination presentation: new-head-arrives from older-appended · case 03

The new-head-arrives event leaves a notification in first-page instead of head-update-pending.

Notification interfaces◈ Members↗
FA-34869

Inbox history pagination presentation: new-head-arrives from older-appended · case 04

The new-head-arrives event leaves a notification in first-page instead of head-update-pending.

Notification interfaces◈ Members↗
FA-34870

Inbox history pagination presentation: new-head-arrives from older-appended · case 05

The new-head-arrives event leaves a notification in first-page instead of head-update-pending.

Notification interfaces◈ Members↗
FA-34871

Inbox history pagination presentation: show-new-head from head-update-pending · case 01

The show-new-head event leaves a notification in first-page instead of head-restoring.

Notification interfaces● Open access↗
FA-34872

Inbox history pagination presentation: show-new-head from head-update-pending · case 02

The show-new-head event leaves a notification in first-page instead of head-restoring.

Notification interfaces◈ Members↗
FA-34873

Inbox history pagination presentation: show-new-head from head-update-pending · case 03

The show-new-head event leaves a notification in first-page instead of head-restoring.

Notification interfaces◈ Members↗
FA-34874

Inbox history pagination presentation: show-new-head from head-update-pending · case 04

The show-new-head event leaves a notification in first-page instead of head-restoring.

Notification interfaces◈ Members↗
FA-34875

Inbox history pagination presentation: show-new-head from head-update-pending · case 05

The show-new-head event leaves a notification in first-page instead of head-restoring.

Notification interfaces◈ Members↗
FA-34876

Inbox history pagination presentation: head-anchor-ready from head-restoring · case 01

The head-anchor-ready event leaves a notification in older-appended instead of first-page.

Notification interfaces● Open access↗
FA-34877

Inbox history pagination presentation: head-anchor-ready from head-restoring · case 02

The head-anchor-ready event leaves a notification in older-appended instead of first-page.

Notification interfaces◈ Members↗
FA-34878

Inbox history pagination presentation: head-anchor-ready from head-restoring · case 03

The head-anchor-ready event leaves a notification in older-appended instead of first-page.

Notification interfaces◈ Members↗
FA-34879

Inbox history pagination presentation: head-anchor-ready from head-restoring · case 04

The head-anchor-ready event leaves a notification in older-appended instead of first-page.

Notification interfaces◈ Members↗
FA-34880

Inbox history pagination presentation: head-anchor-ready from head-restoring · case 05

The head-anchor-ready event leaves a notification in older-appended instead of first-page.

Notification interfaces◈ Members↗
FA-34881

Inbox history pagination presentation: filter-changed from loading-older · case 01

The filter-changed event leaves a notification in older-appended instead of new-filter-loading.

Notification interfaces● Open access↗
FA-34882

Inbox history pagination presentation: filter-changed from loading-older · case 02

The filter-changed event leaves a notification in older-appended instead of new-filter-loading.

Notification interfaces◈ Members↗
FA-34883

Inbox history pagination presentation: filter-changed from loading-older · case 03

The filter-changed event leaves a notification in older-appended instead of new-filter-loading.

Notification interfaces◈ Members↗
FA-34884

Inbox history pagination presentation: filter-changed from loading-older · case 04

The filter-changed event leaves a notification in older-appended instead of new-filter-loading.

Notification interfaces◈ Members↗
FA-34885

Inbox history pagination presentation: filter-changed from loading-older · case 05

The filter-changed event leaves a notification in older-appended instead of new-filter-loading.

Notification interfaces◈ Members↗
FA-34886

Inbox history pagination presentation: old-page-arrives from new-filter-loading · case 01

The old-page-arrives event leaves a notification in older-appended instead of new-filter-loading.

Notification interfaces● Open access↗
FA-34887

Inbox history pagination presentation: old-page-arrives from new-filter-loading · case 02

The old-page-arrives event leaves a notification in older-appended instead of new-filter-loading.

Notification interfaces◈ Members↗
FA-34888

Inbox history pagination presentation: old-page-arrives from new-filter-loading · case 03

The old-page-arrives event leaves a notification in older-appended instead of new-filter-loading.

Notification interfaces◈ Members↗
FA-34889

Inbox history pagination presentation: old-page-arrives from new-filter-loading · case 04

The old-page-arrives event leaves a notification in older-appended instead of new-filter-loading.

Notification interfaces◈ Members↗
FA-34890

Inbox history pagination presentation: old-page-arrives from new-filter-loading · case 05

The old-page-arrives event leaves a notification in older-appended instead of new-filter-loading.

Notification interfaces◈ Members↗
FA-34891

Notification visual impression qualification: enters-viewport from offscreen · case 01

The enters-viewport event leaves a notification in counted instead of qualifying.

Notification interfaces● Open access↗
FA-34892

Notification visual impression qualification: enters-viewport from offscreen · case 02

The enters-viewport event leaves a notification in counted instead of qualifying.

Notification interfaces◈ Members↗
FA-34893

Notification visual impression qualification: enters-viewport from offscreen · case 03

The enters-viewport event leaves a notification in counted instead of qualifying.

Notification interfaces◈ Members↗
FA-34894

Notification visual impression qualification: enters-viewport from offscreen · case 04

The enters-viewport event leaves a notification in counted instead of qualifying.

Notification interfaces◈ Members↗
FA-34895

Notification visual impression qualification: enters-viewport from offscreen · case 05

The enters-viewport event leaves a notification in counted instead of qualifying.

Notification interfaces◈ Members↗
FA-34896

Notification visual impression qualification: exposure-satisfied from qualifying · case 01

The exposure-satisfied event leaves a notification in counted instead of reporting.

Notification interfaces● Open access↗
FA-34897

Notification visual impression qualification: exposure-satisfied from qualifying · case 02

The exposure-satisfied event leaves a notification in counted instead of reporting.

Notification interfaces◈ Members↗
FA-34898

Notification visual impression qualification: exposure-satisfied from qualifying · case 03

The exposure-satisfied event leaves a notification in counted instead of reporting.

Notification interfaces◈ Members↗
FA-34899

Notification visual impression qualification: exposure-satisfied from qualifying · case 04

The exposure-satisfied event leaves a notification in counted instead of reporting.

Notification interfaces◈ Members↗
FA-34900

Notification visual impression qualification: exposure-satisfied from qualifying · case 05

The exposure-satisfied event leaves a notification in counted instead of reporting.

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 ↗