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

Navigating between routes retains resource tags from the abandoned route · case 01

Navigating between routes retains resource tags from the abandoned route.

Client state● Open access↗
FA-24802

Navigating between routes retains resource tags from the abandoned route · case 02

Navigating between routes retains resource tags from the abandoned route.

Client state◈ Members↗
FA-24803

Navigating between routes retains resource tags from the abandoned route · case 03

Navigating between routes retains resource tags from the abandoned route.

Client state◈ Members↗
FA-24804

Navigating between routes retains resource tags from the abandoned route · case 04

Navigating between routes retains resource tags from the abandoned route.

Client state◈ Members↗
FA-24805

Navigating between routes retains resource tags from the abandoned route · case 05

Navigating between routes retains resource tags from the abandoned route.

Client state◈ Members↗
FA-24806

A new navigation inherits transient route-state notices from the previous entry · case 01

A new navigation inherits transient route-state notices from the previous entry.

Client state● Open access↗
FA-24807

A new navigation inherits transient route-state notices from the previous entry · case 02

A new navigation inherits transient route-state notices from the previous entry.

Client state◈ Members↗
FA-24808

A new navigation inherits transient route-state notices from the previous entry · case 03

A new navigation inherits transient route-state notices from the previous entry.

Client state◈ Members↗
FA-24809

A new navigation inherits transient route-state notices from the previous entry · case 04

A new navigation inherits transient route-state notices from the previous entry.

Client state◈ Members↗
FA-24810

A new navigation inherits transient route-state notices from the previous entry · case 05

A new navigation inherits transient route-state notices from the previous entry.

Client state◈ Members↗
FA-24811

Batched store updates notify consumers before all writes become observable · case 01

Batched store updates notify consumers before all writes become observable.

Client state● Open access↗
FA-24812

Batched store updates notify consumers before all writes become observable · case 02

Batched store updates notify consumers before all writes become observable.

Client state◈ Members↗
FA-24813

Batched store updates notify consumers before all writes become observable · case 03

Batched store updates notify consumers before all writes become observable.

Client state◈ Members↗
FA-24814

Batched store updates notify consumers before all writes become observable · case 04

Batched store updates notify consumers before all writes become observable.

Client state◈ Members↗
FA-24815

Batched store updates notify consumers before all writes become observable · case 05

Batched store updates notify consumers before all writes become observable.

Client state◈ Members↗
FA-24816

Cancelling a parent render transition leaves nested work attached · case 01

Cancelling a parent render transition leaves nested work attached.

Client state● Open access↗
FA-24817

Cancelling a parent render transition leaves nested work attached · case 02

Cancelling a parent render transition leaves nested work attached.

Client state◈ Members↗
FA-24818

Cancelling a parent render transition leaves nested work attached · case 03

Cancelling a parent render transition leaves nested work attached.

Client state◈ Members↗
FA-24819

Cancelling a parent render transition leaves nested work attached · case 04

Cancelling a parent render transition leaves nested work attached.

Client state◈ Members↗
FA-24820

Cancelling a parent render transition leaves nested work attached · case 05

Cancelling a parent render transition leaves nested work attached.

Client state◈ Members↗
FA-24821

Continuous client edits postpone a debounced effect forever · case 01

Continuous client edits postpone a debounced effect forever.

Client state● Open access↗
FA-24822

Continuous client edits postpone a debounced effect forever · case 02

Continuous client edits postpone a debounced effect forever.

Client state◈ Members↗
FA-24823

Continuous client edits postpone a debounced effect forever · case 03

Continuous client edits postpone a debounced effect forever.

Client state◈ Members↗
FA-24824

Continuous client edits postpone a debounced effect forever · case 04

Continuous client edits postpone a debounced effect forever.

Client state◈ Members↗
FA-24825

Continuous client edits postpone a debounced effect forever · case 05

Continuous client edits postpone a debounced effect forever.

Client state◈ Members↗
FA-24826

A manual appearance choice is overwritten by a subsequent system preference event · case 01

A manual appearance choice is overwritten by a subsequent system preference event.

Client state● Open access↗
FA-24827

A manual appearance choice is overwritten by a subsequent system preference event · case 02

A manual appearance choice is overwritten by a subsequent system preference event.

Client state◈ Members↗
FA-24828

A manual appearance choice is overwritten by a subsequent system preference event · case 03

A manual appearance choice is overwritten by a subsequent system preference event.

Client state◈ Members↗
FA-24829

A manual appearance choice is overwritten by a subsequent system preference event · case 04

A manual appearance choice is overwritten by a subsequent system preference event.

Client state◈ Members↗
FA-24830

A manual appearance choice is overwritten by a subsequent system preference event · case 05

A manual appearance choice is overwritten by a subsequent system preference event.

Client state◈ Members↗
FA-24831

A resource observer receives fields that belong to another observer selector · case 01

A resource observer receives fields that belong to another observer selector.

Client state● Open access↗
FA-24832

A resource observer receives fields that belong to another observer selector · case 02

A resource observer receives fields that belong to another observer selector.

Client state◈ Members↗
FA-24833

A resource observer receives fields that belong to another observer selector · case 03

A resource observer receives fields that belong to another observer selector.

Client state◈ Members↗
FA-24834

A resource observer receives fields that belong to another observer selector · case 04

A resource observer receives fields that belong to another observer selector.

Client state◈ Members↗
FA-24835

A resource observer receives fields that belong to another observer selector · case 05

A resource observer receives fields that belong to another observer selector.

Client state◈ Members↗
FA-24836

Transferring one buffer view leaves another alias marked readable on the main thread · case 01

Transferring one buffer view leaves another alias marked readable on the main thread.

Client state● Open access↗
FA-24837

Transferring one buffer view leaves another alias marked readable on the main thread · case 02

Transferring one buffer view leaves another alias marked readable on the main thread.

Client state◈ Members↗
FA-24838

Transferring one buffer view leaves another alias marked readable on the main thread · case 03

Transferring one buffer view leaves another alias marked readable on the main thread.

Client state◈ Members↗
FA-24839

Transferring one buffer view leaves another alias marked readable on the main thread · case 04

Transferring one buffer view leaves another alias marked readable on the main thread.

Client state◈ Members↗
FA-24840

Transferring one buffer view leaves another alias marked readable on the main thread · case 05

Transferring one buffer view leaves another alias marked readable on the main thread.

Client state◈ Members↗
FA-24841

Opening a panel seeds its draft from committed constraints · case 01

Opening a panel seeds its draft from committed constraints is violated by the widget projection.

Filter interfaces● Open access↗
FA-24842

Opening a panel seeds its draft from committed constraints · case 02

Opening a panel seeds its draft from committed constraints is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24843

Opening a panel seeds its draft from committed constraints · case 03

Opening a panel seeds its draft from committed constraints is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24844

Opening a panel seeds its draft from committed constraints · case 04

Opening a panel seeds its draft from committed constraints is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24845

Opening a panel seeds its draft from committed constraints · case 05

Opening a panel seeds its draft from committed constraints is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24846

Draft dirtiness ignores ordering but retains constraint identity · case 01

Draft dirtiness ignores ordering but retains constraint identity is violated by the widget projection.

Filter interfaces● Open access↗
FA-24847

Draft dirtiness ignores ordering but retains constraint identity · case 02

Draft dirtiness ignores ordering but retains constraint identity is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24848

Draft dirtiness ignores ordering but retains constraint identity · case 03

Draft dirtiness ignores ordering but retains constraint identity is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24849

Draft dirtiness ignores ordering but retains constraint identity · case 04

Draft dirtiness ignores ordering but retains constraint identity is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24850

Draft dirtiness ignores ordering but retains constraint identity · case 05

Draft dirtiness ignores ordering but retains constraint identity is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24851

Applying rejects a valid but stale draft · case 01

Applying rejects a valid but stale draft is violated by the widget projection.

Filter interfaces● Open access↗
FA-24852

Applying rejects a valid but stale draft · case 02

Applying rejects a valid but stale draft is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24853

Applying rejects a valid but stale draft · case 03

Applying rejects a valid but stale draft is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24854

Applying rejects a valid but stale draft · case 04

Applying rejects a valid but stale draft is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24855

Applying rejects a valid but stale draft · case 05

Applying rejects a valid but stale draft is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24856

Cancel restores the committed snapshot without merging pending constraints · case 01

Cancel restores the committed snapshot without merging pending constraints is violated by the widget projection.

Filter interfaces● Open access↗
FA-24857

Cancel restores the committed snapshot without merging pending constraints · case 02

Cancel restores the committed snapshot without merging pending constraints is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24858

Cancel restores the committed snapshot without merging pending constraints · case 03

Cancel restores the committed snapshot without merging pending constraints is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24859

Cancel restores the committed snapshot without merging pending constraints · case 04

Cancel restores the committed snapshot without merging pending constraints is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24860

Cancel restores the committed snapshot without merging pending constraints · case 05

Cancel restores the committed snapshot without merging pending constraints is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24861

Conflict notices require both a changed revision and a divergent draft · case 01

Conflict notices require both a changed revision and a divergent draft is violated by the widget projection.

Filter interfaces● Open access↗
FA-24862

Conflict notices require both a changed revision and a divergent draft · case 02

Conflict notices require both a changed revision and a divergent draft is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24863

Conflict notices require both a changed revision and a divergent draft · case 03

Conflict notices require both a changed revision and a divergent draft is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24864

Conflict notices require both a changed revision and a divergent draft · case 04

Conflict notices require both a changed revision and a divergent draft is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24865

Conflict notices require both a changed revision and a divergent draft · case 05

Conflict notices require both a changed revision and a divergent draft is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24866

The publish payload uses the validated draft only after revision acceptance · case 01

The publish payload uses the validated draft only after revision acceptance is violated by the widget projection.

Filter interfaces● Open access↗
FA-24867

The publish payload uses the validated draft only after revision acceptance · case 02

The publish payload uses the validated draft only after revision acceptance is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24868

The publish payload uses the validated draft only after revision acceptance · case 03

The publish payload uses the validated draft only after revision acceptance is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24869

The publish payload uses the validated draft only after revision acceptance · case 04

The publish payload uses the validated draft only after revision acceptance is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24870

The publish payload uses the validated draft only after revision acceptance · case 05

The publish payload uses the validated draft only after revision acceptance is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24871

Selected zero-count choices remain enabled for deselection · case 01

Selected zero-count choices remain enabled for deselection is violated by the widget projection.

Filter interfaces● Open access↗
FA-24872

Selected zero-count choices remain enabled for deselection · case 02

Selected zero-count choices remain enabled for deselection is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24873

Selected zero-count choices remain enabled for deselection · case 03

Selected zero-count choices remain enabled for deselection is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24874

Selected zero-count choices remain enabled for deselection · case 04

Selected zero-count choices remain enabled for deselection is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24875

Selected zero-count choices remain enabled for deselection · case 05

Selected zero-count choices remain enabled for deselection is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24876

Unknown facet counts are distinct from zero · case 01

Unknown facet counts are distinct from zero is violated by the widget projection.

Filter interfaces● Open access↗
FA-24877

Unknown facet counts are distinct from zero · case 02

Unknown facet counts are distinct from zero is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24878

Unknown facet counts are distinct from zero · case 03

Unknown facet counts are distinct from zero is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24879

Unknown facet counts are distinct from zero · case 04

Unknown facet counts are distinct from zero is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24880

Unknown facet counts are distinct from zero · case 05

Unknown facet counts are distinct from zero is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24881

Hide-empty retains selected values and unknown counts · case 01

Hide-empty retains selected values and unknown counts is violated by the widget projection.

Filter interfaces● Open access↗
FA-24882

Hide-empty retains selected values and unknown counts · case 02

Hide-empty retains selected values and unknown counts is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24883

Hide-empty retains selected values and unknown counts · case 03

Hide-empty retains selected values and unknown counts is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24884

Hide-empty retains selected values and unknown counts · case 04

Hide-empty retains selected values and unknown counts is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24885

Hide-empty retains selected values and unknown counts · case 05

Hide-empty retains selected values and unknown counts is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24886

Skeleton indicators require loading with no cached count · case 01

Skeleton indicators require loading with no cached count is violated by the widget projection.

Filter interfaces● Open access↗
FA-24887

Skeleton indicators require loading with no cached count · case 02

Skeleton indicators require loading with no cached count is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24888

Skeleton indicators require loading with no cached count · case 03

Skeleton indicators require loading with no cached count is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24889

Skeleton indicators require loading with no cached count · case 04

Skeleton indicators require loading with no cached count is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24890

Skeleton indicators require loading with no cached count · case 05

Skeleton indicators require loading with no cached count is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24891

Empty messages wait for a known settled zero count · case 01

Empty messages wait for a known settled zero count is violated by the widget projection.

Filter interfaces● Open access↗
FA-24892

Empty messages wait for a known settled zero count · case 02

Empty messages wait for a known settled zero count is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24893

Empty messages wait for a known settled zero count · case 03

Empty messages wait for a known settled zero count is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24894

Empty messages wait for a known settled zero count · case 04

Empty messages wait for a known settled zero count is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24895

Empty messages wait for a known settled zero count · case 05

Empty messages wait for a known settled zero count is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24896

Cached zero counts receive a stale marker while refreshing · case 01

Cached zero counts receive a stale marker while refreshing is violated by the widget projection.

Filter interfaces● Open access↗
FA-24897

Cached zero counts receive a stale marker while refreshing · case 02

Cached zero counts receive a stale marker while refreshing is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24898

Cached zero counts receive a stale marker while refreshing · case 03

Cached zero counts receive a stale marker while refreshing is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24899

Cached zero counts receive a stale marker while refreshing · case 04

Cached zero counts receive a stale marker while refreshing is violated by the widget projection.

Filter interfaces◈ Members↗
FA-24900

Cached zero counts receive a stale marker while refreshing · case 05

Cached zero counts receive a stale marker while refreshing is violated by the widget projection.

Filter 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 ↗