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

Exactly one logical request completion: Begin result violates retry transition semantics · case 01

Begin result violates retry transition semantics

HTTP retries● Open access↗FA-30602

Exactly one logical request completion: Begin result violates retry transition semantics · case 02

Begin result violates retry transition semantics

HTTP retries◈ Members↗FA-30603

Exactly one logical request completion: Begin result violates retry transition semantics · case 03

Begin result violates retry transition semantics

HTTP retries◈ Members↗FA-30604

Exactly one logical request completion: Begin result violates retry transition semantics · case 04

Begin result violates retry transition semantics

HTTP retries◈ Members↗FA-30605

Exactly one logical request completion: Begin result violates retry transition semantics · case 05

Begin result violates retry transition semantics

HTTP retries◈ Members↗FA-30606

Exactly one logical request completion: Terminal first violates retry transition semantics · case 01

Terminal first violates retry transition semantics

HTTP retries● Open access↗FA-30607

Exactly one logical request completion: Terminal first violates retry transition semantics · case 02

Terminal first violates retry transition semantics

HTTP retries◈ Members↗FA-30608

Exactly one logical request completion: Terminal first violates retry transition semantics · case 03

Terminal first violates retry transition semantics

HTTP retries◈ Members↗FA-30609

Exactly one logical request completion: Terminal first violates retry transition semantics · case 04

Terminal first violates retry transition semantics

HTTP retries◈ Members↗FA-30610

Exactly one logical request completion: Terminal first violates retry transition semantics · case 05

Terminal first violates retry transition semantics

HTTP retries◈ Members↗FA-30611

Exactly one logical request completion: Initial launch violates retry transition semantics · case 01

Initial launch violates retry transition semantics

HTTP retries● Open access↗FA-30612

Exactly one logical request completion: Initial launch violates retry transition semantics · case 02

Initial launch violates retry transition semantics

HTTP retries◈ Members↗FA-30613

Exactly one logical request completion: Initial launch violates retry transition semantics · case 03

Initial launch violates retry transition semantics

HTTP retries◈ Members↗FA-30614

Exactly one logical request completion: Initial launch violates retry transition semantics · case 04

Initial launch violates retry transition semantics

HTTP retries◈ Members↗FA-30615

Exactly one logical request completion: Initial launch violates retry transition semantics · case 05

Initial launch violates retry transition semantics

HTTP retries◈ Members↗FA-30616

Exactly one logical request completion: Launch generation violates retry transition semantics · case 01

Launch generation violates retry transition semantics

HTTP retries● Open access↗FA-30617

Exactly one logical request completion: Launch generation violates retry transition semantics · case 02

Launch generation violates retry transition semantics

HTTP retries◈ Members↗FA-30618

Exactly one logical request completion: Launch generation violates retry transition semantics · case 03

Launch generation violates retry transition semantics

HTTP retries◈ Members↗FA-30619

Exactly one logical request completion: Launch generation violates retry transition semantics · case 04

Launch generation violates retry transition semantics

HTTP retries◈ Members↗FA-30620

Exactly one logical request completion: Launch generation violates retry transition semantics · case 05

Launch generation violates retry transition semantics

HTTP retries◈ Members↗FA-30621

Exactly one logical request completion: Response active violates retry transition semantics · case 01

Response active violates retry transition semantics

HTTP retries● Open access↗FA-30622

Exactly one logical request completion: Response active violates retry transition semantics · case 02

Response active violates retry transition semantics

HTTP retries◈ Members↗FA-30623

Exactly one logical request completion: Response active violates retry transition semantics · case 03

Response active violates retry transition semantics

HTTP retries◈ Members↗FA-30624

Exactly one logical request completion: Response active violates retry transition semantics · case 04

Response active violates retry transition semantics

HTTP retries◈ Members↗FA-30625

Exactly one logical request completion: Response active violates retry transition semantics · case 05

Response active violates retry transition semantics

HTTP retries◈ Members↗FA-30626

Exactly one logical request completion: Response generation violates retry transition semantics · case 01

Response generation violates retry transition semantics

HTTP retries● Open access↗FA-30627

Exactly one logical request completion: Response generation violates retry transition semantics · case 02

Response generation violates retry transition semantics

HTTP retries◈ Members↗FA-30628

Exactly one logical request completion: Response generation violates retry transition semantics · case 03

Response generation violates retry transition semantics

HTTP retries◈ Members↗FA-30629

Exactly one logical request completion: Response generation violates retry transition semantics · case 04

Response generation violates retry transition semantics

HTTP retries◈ Members↗FA-30630

Exactly one logical request completion: Response generation violates retry transition semantics · case 05

Response generation violates retry transition semantics

HTTP retries◈ Members↗FA-30631

Exactly one logical request completion: Response consumed violates retry transition semantics · case 01

Response consumed violates retry transition semantics

HTTP retries● Open access↗FA-30632

Exactly one logical request completion: Response consumed violates retry transition semantics · case 02

Response consumed violates retry transition semantics

HTTP retries◈ Members↗FA-30633

Exactly one logical request completion: Response consumed violates retry transition semantics · case 03

Response consumed violates retry transition semantics

HTTP retries◈ Members↗FA-30634

Exactly one logical request completion: Response consumed violates retry transition semantics · case 04

Response consumed violates retry transition semantics

HTTP retries◈ Members↗FA-30635

Exactly one logical request completion: Response consumed violates retry transition semantics · case 05

Response consumed violates retry transition semantics

HTTP retries◈ Members↗FA-30636

Exactly one logical request completion: Success upper violates retry transition semantics · case 01

Success upper violates retry transition semantics

HTTP retries● Open access↗FA-30637

Exactly one logical request completion: Success upper violates retry transition semantics · case 02

Success upper violates retry transition semantics

HTTP retries◈ Members↗FA-30638

Exactly one logical request completion: Success upper violates retry transition semantics · case 03

Success upper violates retry transition semantics

HTTP retries◈ Members↗FA-30639

Exactly one logical request completion: Success upper violates retry transition semantics · case 04

Success upper violates retry transition semantics

HTTP retries◈ Members↗FA-30640

Exactly one logical request completion: Success upper violates retry transition semantics · case 05

Success upper violates retry transition semantics

HTTP retries◈ Members↗FA-30641

Exactly one logical request completion: Success lower violates retry transition semantics · case 01

Success lower violates retry transition semantics

HTTP retries● Open access↗FA-30642

Exactly one logical request completion: Success lower violates retry transition semantics · case 02

Success lower violates retry transition semantics

HTTP retries◈ Members↗FA-30643

Exactly one logical request completion: Success lower violates retry transition semantics · case 03

Success lower violates retry transition semantics

HTTP retries◈ Members↗FA-30644

Exactly one logical request completion: Success lower violates retry transition semantics · case 04

Success lower violates retry transition semantics

HTTP retries◈ Members↗FA-30645

Exactly one logical request completion: Success lower violates retry transition semantics · case 05

Success lower violates retry transition semantics

HTTP retries◈ Members↗FA-30646

Exactly one logical request completion: Success payload violates retry transition semantics · case 01

Success payload violates retry transition semantics

HTTP retries● Open access↗FA-30647

Exactly one logical request completion: Success payload violates retry transition semantics · case 02

Success payload violates retry transition semantics

HTTP retries◈ Members↗FA-30648

Exactly one logical request completion: Success payload violates retry transition semantics · case 03

Success payload violates retry transition semantics

HTTP retries◈ Members↗FA-30649

Exactly one logical request completion: Success payload violates retry transition semantics · case 04

Success payload violates retry transition semantics

HTTP retries◈ Members↗FA-30650

Exactly one logical request completion: Success payload violates retry transition semantics · case 05

Success payload violates retry transition semantics

HTTP retries◈ Members↗FA-30651

Exactly one logical request completion: Retry statuses violates retry transition semantics · case 01

Retry statuses violates retry transition semantics

HTTP retries● Open access↗FA-30652

Exactly one logical request completion: Retry statuses violates retry transition semantics · case 02

Retry statuses violates retry transition semantics

HTTP retries◈ Members↗FA-30653

Exactly one logical request completion: Retry statuses violates retry transition semantics · case 03

Retry statuses violates retry transition semantics

HTTP retries◈ Members↗FA-30654

Exactly one logical request completion: Retry statuses violates retry transition semantics · case 04

Retry statuses violates retry transition semantics

HTTP retries◈ Members↗FA-30655

Exactly one logical request completion: Retry statuses violates retry transition semantics · case 05

Retry statuses violates retry transition semantics

HTTP retries◈ Members↗FA-30656

Exactly one logical request completion: Failure status violates retry transition semantics · case 01

Failure status violates retry transition semantics

HTTP retries● Open access↗FA-30657

Exactly one logical request completion: Failure status violates retry transition semantics · case 02

Failure status violates retry transition semantics

HTTP retries◈ Members↗FA-30658

Exactly one logical request completion: Failure status violates retry transition semantics · case 03

Failure status violates retry transition semantics

HTTP retries◈ Members↗FA-30659

Exactly one logical request completion: Failure status violates retry transition semantics · case 04

Failure status violates retry transition semantics

HTTP retries◈ Members↗FA-30660

Exactly one logical request completion: Failure status violates retry transition semantics · case 05

Failure status violates retry transition semantics

HTTP retries◈ Members↗FA-30661

Exactly one logical request completion: Retry token gate violates retry transition semantics · case 01

Retry token gate violates retry transition semantics

HTTP retries● Open access↗FA-30662

Exactly one logical request completion: Retry token gate violates retry transition semantics · case 02

Retry token gate violates retry transition semantics

HTTP retries◈ Members↗FA-30663

Exactly one logical request completion: Retry token gate violates retry transition semantics · case 03

Retry token gate violates retry transition semantics

HTTP retries◈ Members↗FA-30664

Exactly one logical request completion: Retry token gate violates retry transition semantics · case 04

Retry token gate violates retry transition semantics

HTTP retries◈ Members↗FA-30665

Exactly one logical request completion: Retry token gate violates retry transition semantics · case 05

Retry token gate violates retry transition semantics

HTTP retries◈ Members↗FA-30666

Exactly one logical request completion: Retry generation violates retry transition semantics · case 01

Retry generation violates retry transition semantics

HTTP retries● Open access↗FA-30667

Exactly one logical request completion: Retry generation violates retry transition semantics · case 02

Retry generation violates retry transition semantics

HTTP retries◈ Members↗FA-30668

Exactly one logical request completion: Retry generation violates retry transition semantics · case 03

Retry generation violates retry transition semantics

HTTP retries◈ Members↗FA-30669

Exactly one logical request completion: Retry generation violates retry transition semantics · case 04

Retry generation violates retry transition semantics

HTTP retries◈ Members↗FA-30670

Exactly one logical request completion: Retry generation violates retry transition semantics · case 05

Retry generation violates retry transition semantics

HTTP retries◈ Members↗FA-30671

Exactly one logical request completion: Cancel final violates retry transition semantics · case 01

Cancel final violates retry transition semantics

HTTP retries● Open access↗FA-30672

Exactly one logical request completion: Cancel final violates retry transition semantics · case 02

Cancel final violates retry transition semantics

HTTP retries◈ Members↗FA-30673

Exactly one logical request completion: Cancel final violates retry transition semantics · case 03

Cancel final violates retry transition semantics

HTTP retries◈ Members↗FA-30674

Exactly one logical request completion: Cancel final violates retry transition semantics · case 04

Cancel final violates retry transition semantics

HTTP retries◈ Members↗FA-30675

Exactly one logical request completion: Cancel final violates retry transition semantics · case 05

Cancel final violates retry transition semantics

HTTP retries◈ Members↗FA-30676

Retry advice across wall and monotonic clocks: Server date violates retry transition semantics · case 01

Server date violates retry transition semantics

HTTP retries● Open access↗FA-30677

Retry advice across wall and monotonic clocks: Server date violates retry transition semantics · case 02

Server date violates retry transition semantics

HTTP retries◈ Members↗FA-30678

Retry advice across wall and monotonic clocks: Server date violates retry transition semantics · case 03

Server date violates retry transition semantics

HTTP retries◈ Members↗FA-30679

Retry advice across wall and monotonic clocks: Server date violates retry transition semantics · case 04

Server date violates retry transition semantics

HTTP retries◈ Members↗FA-30680

Retry advice across wall and monotonic clocks: Server date violates retry transition semantics · case 05

Server date violates retry transition semantics

HTTP retries◈ Members↗FA-30681

Retry advice across wall and monotonic clocks: Age origin violates retry transition semantics · case 01

Age origin violates retry transition semantics

HTTP retries● Open access↗FA-30682

Retry advice across wall and monotonic clocks: Age origin violates retry transition semantics · case 02

Age origin violates retry transition semantics

HTTP retries◈ Members↗FA-30683

Retry advice across wall and monotonic clocks: Age origin violates retry transition semantics · case 03

Age origin violates retry transition semantics

HTTP retries◈ Members↗FA-30684

Retry advice across wall and monotonic clocks: Age origin violates retry transition semantics · case 04

Age origin violates retry transition semantics

HTTP retries◈ Members↗FA-30685

Retry advice across wall and monotonic clocks: Age origin violates retry transition semantics · case 05

Age origin violates retry transition semantics

HTTP retries◈ Members↗FA-30686

Retry advice across wall and monotonic clocks: Receive monotonic violates retry transition semantics · case 01

Receive monotonic violates retry transition semantics

HTTP retries● Open access↗FA-30687

Retry advice across wall and monotonic clocks: Receive monotonic violates retry transition semantics · case 02

Receive monotonic violates retry transition semantics

HTTP retries◈ Members↗FA-30688

Retry advice across wall and monotonic clocks: Receive monotonic violates retry transition semantics · case 03

Receive monotonic violates retry transition semantics

HTTP retries◈ Members↗FA-30689

Retry advice across wall and monotonic clocks: Receive monotonic violates retry transition semantics · case 04

Receive monotonic violates retry transition semantics

HTTP retries◈ Members↗FA-30690

Retry advice across wall and monotonic clocks: Receive monotonic violates retry transition semantics · case 05

Receive monotonic violates retry transition semantics

HTTP retries◈ Members↗FA-30691

Retry advice across wall and monotonic clocks: Fallback wall violates retry transition semantics · case 01

Fallback wall violates retry transition semantics

HTTP retries● Open access↗FA-30692

Retry advice across wall and monotonic clocks: Fallback wall violates retry transition semantics · case 02

Fallback wall violates retry transition semantics

HTTP retries◈ Members↗FA-30693

Retry advice across wall and monotonic clocks: Fallback wall violates retry transition semantics · case 03

Fallback wall violates retry transition semantics

HTTP retries◈ Members↗FA-30694

Retry advice across wall and monotonic clocks: Fallback wall violates retry transition semantics · case 04

Fallback wall violates retry transition semantics

HTTP retries◈ Members↗FA-30695

Retry advice across wall and monotonic clocks: Fallback wall violates retry transition semantics · case 05

Fallback wall violates retry transition semantics

HTTP retries◈ Members↗FA-30696

Retry advice across wall and monotonic clocks: Response reset violates retry transition semantics · case 01

Response reset violates retry transition semantics

HTTP retries● Open access↗FA-30697

Retry advice across wall and monotonic clocks: Response reset violates retry transition semantics · case 02

Response reset violates retry transition semantics

HTTP retries◈ Members↗FA-30698

Retry advice across wall and monotonic clocks: Response reset violates retry transition semantics · case 03

Response reset violates retry transition semantics

HTTP retries◈ Members↗FA-30699

Retry advice across wall and monotonic clocks: Response reset violates retry transition semantics · case 04

Response reset violates retry transition semantics

HTTP retries◈ Members↗FA-30700

Retry advice across wall and monotonic clocks: Response reset violates retry transition semantics · case 05

Response reset violates retry transition semantics

HTTP retries◈ 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 ↗