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

Client preference layer resolution: Writable preference projection · case 01

Writable preference projection.

Client state● Open access↗
FA-24702

Client preference layer resolution: Writable preference projection · case 02

Writable preference projection.

Client state◈ Members↗
FA-24703

Client preference layer resolution: Writable preference projection · case 03

Writable preference projection.

Client state◈ Members↗
FA-24704

Client preference layer resolution: Writable preference projection · case 04

Writable preference projection.

Client state◈ Members↗
FA-24705

Client preference layer resolution: Writable preference projection · case 05

Writable preference projection.

Client state◈ Members↗
FA-24706

Client preference layer resolution: Preference source attribution · case 01

Preference source attribution.

Client state● Open access↗
FA-24707

Client preference layer resolution: Preference source attribution · case 02

Preference source attribution.

Client state◈ Members↗
FA-24708

Client preference layer resolution: Preference source attribution · case 03

Preference source attribution.

Client state◈ Members↗
FA-24709

Client preference layer resolution: Preference source attribution · case 04

Preference source attribution.

Client state◈ Members↗
FA-24710

Client preference layer resolution: Preference source attribution · case 05

Preference source attribution.

Client state◈ Members↗
FA-24711

Client preference layer resolution: Redundant device override pruning · case 01

Redundant device override pruning.

Client state● Open access↗
FA-24712

Client preference layer resolution: Redundant device override pruning · case 02

Redundant device override pruning.

Client state◈ Members↗
FA-24713

Client preference layer resolution: Redundant device override pruning · case 03

Redundant device override pruning.

Client state◈ Members↗
FA-24714

Client preference layer resolution: Redundant device override pruning · case 04

Redundant device override pruning.

Client state◈ Members↗
FA-24715

Client preference layer resolution: Redundant device override pruning · case 05

Redundant device override pruning.

Client state◈ Members↗
FA-24716

Client preference layer resolution: Workspace lock report · case 01

Workspace lock report.

Client state● Open access↗
FA-24717

Client preference layer resolution: Workspace lock report · case 02

Workspace lock report.

Client state◈ Members↗
FA-24718

Client preference layer resolution: Workspace lock report · case 03

Workspace lock report.

Client state◈ Members↗
FA-24719

Client preference layer resolution: Workspace lock report · case 04

Workspace lock report.

Client state◈ Members↗
FA-24720

Client preference layer resolution: Workspace lock report · case 05

Workspace lock report.

Client state◈ Members↗
FA-24721

A nested route failure clears unrelated loaded segments · case 01

A nested route failure clears unrelated loaded segments.

Client state● Open access↗
FA-24722

A nested route failure clears unrelated loaded segments · case 02

A nested route failure clears unrelated loaded segments.

Client state◈ Members↗
FA-24723

A nested route failure clears unrelated loaded segments · case 03

A nested route failure clears unrelated loaded segments.

Client state◈ Members↗
FA-24724

A nested route failure clears unrelated loaded segments · case 04

A nested route failure clears unrelated loaded segments.

Client state◈ Members↗
FA-24725

A nested route failure clears unrelated loaded segments · case 05

A nested route failure clears unrelated loaded segments.

Client state◈ Members↗
FA-24726

A committed transition leaves its dependent render lanes pending · case 01

A committed transition leaves its dependent render lanes pending.

Client state● Open access↗
FA-24727

A committed transition leaves its dependent render lanes pending · case 02

A committed transition leaves its dependent render lanes pending.

Client state◈ Members↗
FA-24728

A committed transition leaves its dependent render lanes pending · case 03

A committed transition leaves its dependent render lanes pending.

Client state◈ Members↗
FA-24729

A committed transition leaves its dependent render lanes pending · case 04

A committed transition leaves its dependent render lanes pending.

Client state◈ Members↗
FA-24730

A committed transition leaves its dependent render lanes pending · case 05

A committed transition leaves its dependent render lanes pending.

Client state◈ Members↗
FA-24731

A successful background refresh leaves the preceding error attempt visible · case 01

A successful background refresh leaves the preceding error attempt visible.

Client state● Open access↗
FA-24732

A successful background refresh leaves the preceding error attempt visible · case 02

A successful background refresh leaves the preceding error attempt visible.

Client state◈ Members↗
FA-24733

A successful background refresh leaves the preceding error attempt visible · case 03

A successful background refresh leaves the preceding error attempt visible.

Client state◈ Members↗
FA-24734

A successful background refresh leaves the preceding error attempt visible · case 04

A successful background refresh leaves the preceding error attempt visible.

Client state◈ Members↗
FA-24735

A successful background refresh leaves the preceding error attempt visible · case 05

A successful background refresh leaves the preceding error attempt visible.

Client state◈ Members↗
FA-24736

External-store selectors rerun for unrelated changed paths · case 01

External-store selectors rerun for unrelated changed paths.

Client state● Open access↗
FA-24737

External-store selectors rerun for unrelated changed paths · case 02

External-store selectors rerun for unrelated changed paths.

Client state◈ Members↗
FA-24738

External-store selectors rerun for unrelated changed paths · case 03

External-store selectors rerun for unrelated changed paths.

Client state◈ Members↗
FA-24739

External-store selectors rerun for unrelated changed paths · case 04

External-store selectors rerun for unrelated changed paths.

Client state◈ Members↗
FA-24740

External-store selectors rerun for unrelated changed paths · case 05

External-store selectors rerun for unrelated changed paths.

Client state◈ Members↗
FA-24741

A child loader is started before its parent route data is available · case 01

A child loader is started before its parent route data is available.

Client state● Open access↗
FA-24742

A child loader is started before its parent route data is available · case 02

A child loader is started before its parent route data is available.

Client state◈ Members↗
FA-24743

A child loader is started before its parent route data is available · case 03

A child loader is started before its parent route data is available.

Client state◈ Members↗
FA-24744

A child loader is started before its parent route data is available · case 04

A child loader is started before its parent route data is available.

Client state◈ Members↗
FA-24745

A child loader is started before its parent route data is available · case 05

A child loader is started before its parent route data is available.

Client state◈ Members↗
FA-24746

A pointer leaves a link but its speculative prefetch still starts · case 01

A pointer leaves a link but its speculative prefetch still starts.

Client state● Open access↗
FA-24747

A pointer leaves a link but its speculative prefetch still starts · case 02

A pointer leaves a link but its speculative prefetch still starts.

Client state◈ Members↗
FA-24748

A pointer leaves a link but its speculative prefetch still starts · case 03

A pointer leaves a link but its speculative prefetch still starts.

Client state◈ Members↗
FA-24749

A pointer leaves a link but its speculative prefetch still starts · case 04

A pointer leaves a link but its speculative prefetch still starts.

Client state◈ Members↗
FA-24750

A pointer leaves a link but its speculative prefetch still starts · case 05

A pointer leaves a link but its speculative prefetch still starts.

Client state◈ Members↗
FA-24751

Effect teardown stops after one disposer fails · case 01

Effect teardown stops after one disposer fails.

Client state● Open access↗
FA-24752

Effect teardown stops after one disposer fails · case 02

Effect teardown stops after one disposer fails.

Client state◈ Members↗
FA-24753

Effect teardown stops after one disposer fails · case 03

Effect teardown stops after one disposer fails.

Client state◈ Members↗
FA-24754

Effect teardown stops after one disposer fails · case 04

Effect teardown stops after one disposer fails.

Client state◈ Members↗
FA-24755

Effect teardown stops after one disposer fails · case 05

Effect teardown stops after one disposer fails.

Client state◈ Members↗
FA-24756

A removed workspace leaves the client on an inaccessible last-visited workspace · case 01

A removed workspace leaves the client on an inaccessible last-visited workspace.

Client state● Open access↗
FA-24757

A removed workspace leaves the client on an inaccessible last-visited workspace · case 02

A removed workspace leaves the client on an inaccessible last-visited workspace.

Client state◈ Members↗
FA-24758

A removed workspace leaves the client on an inaccessible last-visited workspace · case 03

A removed workspace leaves the client on an inaccessible last-visited workspace.

Client state◈ Members↗
FA-24759

A removed workspace leaves the client on an inaccessible last-visited workspace · case 04

A removed workspace leaves the client on an inaccessible last-visited workspace.

Client state◈ Members↗
FA-24760

A removed workspace leaves the client on an inaccessible last-visited workspace · case 05

A removed workspace leaves the client on an inaccessible last-visited workspace.

Client state◈ Members↗
FA-24761

Store writes notify a hydrating consumer before its server snapshot is released · case 01

Store writes notify a hydrating consumer before its server snapshot is released.

Client state● Open access↗
FA-24762

Store writes notify a hydrating consumer before its server snapshot is released · case 02

Store writes notify a hydrating consumer before its server snapshot is released.

Client state◈ Members↗
FA-24763

Store writes notify a hydrating consumer before its server snapshot is released · case 03

Store writes notify a hydrating consumer before its server snapshot is released.

Client state◈ Members↗
FA-24764

Store writes notify a hydrating consumer before its server snapshot is released · case 04

Store writes notify a hydrating consumer before its server snapshot is released.

Client state◈ Members↗
FA-24765

Store writes notify a hydrating consumer before its server snapshot is released · case 05

Store writes notify a hydrating consumer before its server snapshot is released.

Client state◈ Members↗
FA-24766

A selector cache leaks one consumer selector result into another consumer · case 01

A selector cache leaks one consumer selector result into another consumer.

Client state● Open access↗
FA-24767

A selector cache leaks one consumer selector result into another consumer · case 02

A selector cache leaks one consumer selector result into another consumer.

Client state◈ Members↗
FA-24768

A selector cache leaks one consumer selector result into another consumer · case 03

A selector cache leaks one consumer selector result into another consumer.

Client state◈ Members↗
FA-24769

A selector cache leaks one consumer selector result into another consumer · case 04

A selector cache leaks one consumer selector result into another consumer.

Client state◈ Members↗
FA-24770

A selector cache leaks one consumer selector result into another consumer · case 05

A selector cache leaks one consumer selector result into another consumer.

Client state◈ Members↗
FA-24771

Skipping deferred updates changes the order of a later urgent replay · case 01

Skipping deferred updates changes the order of a later urgent replay.

Client state● Open access↗
FA-24772

Skipping deferred updates changes the order of a later urgent replay · case 02

Skipping deferred updates changes the order of a later urgent replay.

Client state◈ Members↗
FA-24773

Skipping deferred updates changes the order of a later urgent replay · case 03

Skipping deferred updates changes the order of a later urgent replay.

Client state◈ Members↗
FA-24774

Skipping deferred updates changes the order of a later urgent replay · case 04

Skipping deferred updates changes the order of a later urgent replay.

Client state◈ Members↗
FA-24775

Skipping deferred updates changes the order of a later urgent replay · case 05

Skipping deferred updates changes the order of a later urgent replay.

Client state◈ Members↗
FA-24776

A transition disappears while one of its spawned child tasks remains unresolved · case 01

A transition disappears while one of its spawned child tasks remains unresolved.

Client state● Open access↗
FA-24777

A transition disappears while one of its spawned child tasks remains unresolved · case 02

A transition disappears while one of its spawned child tasks remains unresolved.

Client state◈ Members↗
FA-24778

A transition disappears while one of its spawned child tasks remains unresolved · case 03

A transition disappears while one of its spawned child tasks remains unresolved.

Client state◈ Members↗
FA-24779

A transition disappears while one of its spawned child tasks remains unresolved · case 04

A transition disappears while one of its spawned child tasks remains unresolved.

Client state◈ Members↗
FA-24780

A transition disappears while one of its spawned child tasks remains unresolved · case 05

A transition disappears while one of its spawned child tasks remains unresolved.

Client state◈ Members↗
FA-24781

Workspace draft eviction discards unsaved work to meet a retention cap · case 01

Workspace draft eviction discards unsaved work to meet a retention cap.

Client state● Open access↗
FA-24782

Workspace draft eviction discards unsaved work to meet a retention cap · case 02

Workspace draft eviction discards unsaved work to meet a retention cap.

Client state◈ Members↗
FA-24783

Workspace draft eviction discards unsaved work to meet a retention cap · case 03

Workspace draft eviction discards unsaved work to meet a retention cap.

Client state◈ Members↗
FA-24784

Workspace draft eviction discards unsaved work to meet a retention cap · case 04

Workspace draft eviction discards unsaved work to meet a retention cap.

Client state◈ Members↗
FA-24785

Workspace draft eviction discards unsaved work to meet a retention cap · case 05

Workspace draft eviction discards unsaved work to meet a retention cap.

Client state◈ Members↗
FA-24786

Preference reset is serialized as a null assignment instead of removing the override · case 01

Preference reset is serialized as a null assignment instead of removing the override.

Client state● Open access↗
FA-24787

Preference reset is serialized as a null assignment instead of removing the override · case 02

Preference reset is serialized as a null assignment instead of removing the override.

Client state◈ Members↗
FA-24788

Preference reset is serialized as a null assignment instead of removing the override · case 03

Preference reset is serialized as a null assignment instead of removing the override.

Client state◈ Members↗
FA-24789

Preference reset is serialized as a null assignment instead of removing the override · case 04

Preference reset is serialized as a null assignment instead of removing the override.

Client state◈ Members↗
FA-24790

Preference reset is serialized as a null assignment instead of removing the override · case 05

Preference reset is serialized as a null assignment instead of removing the override.

Client state◈ Members↗
FA-24791

Replacing generated file content revokes the blob URL still used by a reader · case 01

Replacing generated file content revokes the blob URL still used by a reader.

Client state● Open access↗
FA-24792

Replacing generated file content revokes the blob URL still used by a reader · case 02

Replacing generated file content revokes the blob URL still used by a reader.

Client state◈ Members↗
FA-24793

Replacing generated file content revokes the blob URL still used by a reader · case 03

Replacing generated file content revokes the blob URL still used by a reader.

Client state◈ Members↗
FA-24794

Replacing generated file content revokes the blob URL still used by a reader · case 04

Replacing generated file content revokes the blob URL still used by a reader.

Client state◈ Members↗
FA-24795

Replacing generated file content revokes the blob URL still used by a reader · case 05

Replacing generated file content revokes the blob URL still used by a reader.

Client state◈ Members↗
FA-24796

Autosave coalescing drops a field edit made while its preceding value is in flight · case 01

Autosave coalescing drops a field edit made while its preceding value is in flight.

Client state● Open access↗
FA-24797

Autosave coalescing drops a field edit made while its preceding value is in flight · case 02

Autosave coalescing drops a field edit made while its preceding value is in flight.

Client state◈ Members↗
FA-24798

Autosave coalescing drops a field edit made while its preceding value is in flight · case 03

Autosave coalescing drops a field edit made while its preceding value is in flight.

Client state◈ Members↗
FA-24799

Autosave coalescing drops a field edit made while its preceding value is in flight · case 04

Autosave coalescing drops a field edit made while its preceding value is in flight.

Client state◈ Members↗
FA-24800

Autosave coalescing drops a field edit made while its preceding value is in flight · case 05

Autosave coalescing drops a field edit made while its preceding value is in flight.

Client state◈ 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 ↗