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

Logical request deadline across retry phases: Queue expiry violates retry transition semantics · case 01

Queue expiry violates retry transition semantics

HTTP retries● Open access↗FA-30402

Logical request deadline across retry phases: Queue expiry violates retry transition semantics · case 02

Queue expiry violates retry transition semantics

HTTP retries◈ Members↗FA-30403

Logical request deadline across retry phases: Queue expiry violates retry transition semantics · case 03

Queue expiry violates retry transition semantics

HTTP retries◈ Members↗FA-30404

Logical request deadline across retry phases: Queue expiry violates retry transition semantics · case 04

Queue expiry violates retry transition semantics

HTTP retries◈ Members↗FA-30405

Logical request deadline across retry phases: Queue expiry violates retry transition semantics · case 05

Queue expiry violates retry transition semantics

HTTP retries◈ Members↗FA-30406

Logical request deadline across retry phases: Delay origin violates retry transition semantics · case 01

Delay origin violates retry transition semantics

HTTP retries● Open access↗FA-30407

Logical request deadline across retry phases: Delay origin violates retry transition semantics · case 02

Delay origin violates retry transition semantics

HTTP retries◈ Members↗FA-30408

Logical request deadline across retry phases: Delay origin violates retry transition semantics · case 03

Delay origin violates retry transition semantics

HTTP retries◈ Members↗FA-30409

Logical request deadline across retry phases: Delay origin violates retry transition semantics · case 04

Delay origin violates retry transition semantics

HTTP retries◈ Members↗FA-30410

Logical request deadline across retry phases: Delay origin violates retry transition semantics · case 05

Delay origin violates retry transition semantics

HTTP retries◈ Members↗FA-30411

Logical request deadline across retry phases: Queue single violates retry transition semantics · case 01

Queue single violates retry transition semantics

HTTP retries● Open access↗FA-30412

Logical request deadline across retry phases: Queue single violates retry transition semantics · case 02

Queue single violates retry transition semantics

HTTP retries◈ Members↗FA-30413

Logical request deadline across retry phases: Queue single violates retry transition semantics · case 03

Queue single violates retry transition semantics

HTTP retries◈ Members↗FA-30414

Logical request deadline across retry phases: Queue single violates retry transition semantics · case 04

Queue single violates retry transition semantics

HTTP retries◈ Members↗FA-30415

Logical request deadline across retry phases: Queue single violates retry transition semantics · case 05

Queue single violates retry transition semantics

HTTP retries◈ Members↗FA-30416

Logical request deadline across retry phases: Wake state violates retry transition semantics · case 01

Wake state violates retry transition semantics

HTTP retries● Open access↗FA-30417

Logical request deadline across retry phases: Wake state violates retry transition semantics · case 02

Wake state violates retry transition semantics

HTTP retries◈ Members↗FA-30418

Logical request deadline across retry phases: Wake state violates retry transition semantics · case 03

Wake state violates retry transition semantics

HTTP retries◈ Members↗FA-30419

Logical request deadline across retry phases: Wake state violates retry transition semantics · case 04

Wake state violates retry transition semantics

HTTP retries◈ Members↗FA-30420

Logical request deadline across retry phases: Wake state violates retry transition semantics · case 05

Wake state violates retry transition semantics

HTTP retries◈ Members↗FA-30421

Logical request deadline across retry phases: Wake expiry violates retry transition semantics · case 01

Wake expiry violates retry transition semantics

HTTP retries● Open access↗FA-30422

Logical request deadline across retry phases: Wake expiry violates retry transition semantics · case 02

Wake expiry violates retry transition semantics

HTTP retries◈ Members↗FA-30423

Logical request deadline across retry phases: Wake expiry violates retry transition semantics · case 03

Wake expiry violates retry transition semantics

HTTP retries◈ Members↗FA-30424

Logical request deadline across retry phases: Wake expiry violates retry transition semantics · case 04

Wake expiry violates retry transition semantics

HTTP retries◈ Members↗FA-30425

Logical request deadline across retry phases: Wake expiry violates retry transition semantics · case 05

Wake expiry violates retry transition semantics

HTTP retries◈ Members↗FA-30426

Logical request deadline across retry phases: Wake due violates retry transition semantics · case 01

Wake due violates retry transition semantics

HTTP retries● Open access↗FA-30427

Logical request deadline across retry phases: Wake due violates retry transition semantics · case 02

Wake due violates retry transition semantics

HTTP retries◈ Members↗FA-30428

Logical request deadline across retry phases: Wake due violates retry transition semantics · case 03

Wake due violates retry transition semantics

HTTP retries◈ Members↗FA-30429

Logical request deadline across retry phases: Wake due violates retry transition semantics · case 04

Wake due violates retry transition semantics

HTTP retries◈ Members↗FA-30430

Logical request deadline across retry phases: Wake due violates retry transition semantics · case 05

Wake due violates retry transition semantics

HTTP retries◈ Members↗FA-30431

Logical request deadline across retry phases: Running state violates retry transition semantics · case 01

Running state violates retry transition semantics

HTTP retries● Open access↗FA-30432

Logical request deadline across retry phases: Running state violates retry transition semantics · case 02

Running state violates retry transition semantics

HTTP retries◈ Members↗FA-30433

Logical request deadline across retry phases: Running state violates retry transition semantics · case 03

Running state violates retry transition semantics

HTTP retries◈ Members↗FA-30434

Logical request deadline across retry phases: Running state violates retry transition semantics · case 04

Running state violates retry transition semantics

HTTP retries◈ Members↗FA-30435

Logical request deadline across retry phases: Running state violates retry transition semantics · case 05

Running state violates retry transition semantics

HTTP retries◈ Members↗FA-30436

Logical request deadline across retry phases: Failure state violates retry transition semantics · case 01

Failure state violates retry transition semantics

HTTP retries● Open access↗FA-30437

Logical request deadline across retry phases: Failure state violates retry transition semantics · case 02

Failure state violates retry transition semantics

HTTP retries◈ Members↗FA-30438

Logical request deadline across retry phases: Failure state violates retry transition semantics · case 03

Failure state violates retry transition semantics

HTTP retries◈ Members↗FA-30439

Logical request deadline across retry phases: Failure state violates retry transition semantics · case 04

Failure state violates retry transition semantics

HTTP retries◈ Members↗FA-30440

Logical request deadline across retry phases: Failure state violates retry transition semantics · case 05

Failure state violates retry transition semantics

HTTP retries◈ Members↗FA-30441

Logical request deadline across retry phases: Complete expiry violates retry transition semantics · case 01

Complete expiry violates retry transition semantics

HTTP retries● Open access↗FA-30442

Logical request deadline across retry phases: Complete expiry violates retry transition semantics · case 02

Complete expiry violates retry transition semantics

HTTP retries◈ Members↗FA-30443

Logical request deadline across retry phases: Complete expiry violates retry transition semantics · case 03

Complete expiry violates retry transition semantics

HTTP retries◈ Members↗FA-30444

Logical request deadline across retry phases: Complete expiry violates retry transition semantics · case 04

Complete expiry violates retry transition semantics

HTTP retries◈ Members↗FA-30445

Logical request deadline across retry phases: Complete expiry violates retry transition semantics · case 05

Complete expiry violates retry transition semantics

HTTP retries◈ Members↗FA-30446

Logical request deadline across retry phases: Complete terminal violates retry transition semantics · case 01

Complete terminal violates retry transition semantics

HTTP retries● Open access↗FA-30447

Logical request deadline across retry phases: Complete terminal violates retry transition semantics · case 02

Complete terminal violates retry transition semantics

HTTP retries◈ Members↗FA-30448

Logical request deadline across retry phases: Complete terminal violates retry transition semantics · case 03

Complete terminal violates retry transition semantics

HTTP retries◈ Members↗FA-30449

Logical request deadline across retry phases: Complete terminal violates retry transition semantics · case 04

Complete terminal violates retry transition semantics

HTTP retries◈ Members↗FA-30450

Logical request deadline across retry phases: Complete terminal violates retry transition semantics · case 05

Complete terminal violates retry transition semantics

HTTP retries◈ Members↗FA-30451

Retry routing with origin affinity: Pool order violates retry transition semantics · case 01

Pool order violates retry transition semantics

HTTP retries● Open access↗FA-30452

Retry routing with origin affinity: Pool order violates retry transition semantics · case 02

Pool order violates retry transition semantics

HTTP retries◈ Members↗FA-30453

Retry routing with origin affinity: Pool order violates retry transition semantics · case 03

Pool order violates retry transition semantics

HTTP retries◈ Members↗FA-30454

Retry routing with origin affinity: Pool order violates retry transition semantics · case 04

Pool order violates retry transition semantics

HTTP retries◈ Members↗FA-30455

Retry routing with origin affinity: Pool order violates retry transition semantics · case 05

Pool order violates retry transition semantics

HTTP retries◈ Members↗FA-30456

Retry routing with origin affinity: Request reset violates retry transition semantics · case 01

Request reset violates retry transition semantics

HTTP retries● Open access↗FA-30457

Retry routing with origin affinity: Request reset violates retry transition semantics · case 02

Request reset violates retry transition semantics

HTTP retries◈ Members↗FA-30458

Retry routing with origin affinity: Request reset violates retry transition semantics · case 03

Request reset violates retry transition semantics

HTTP retries◈ Members↗FA-30459

Retry routing with origin affinity: Request reset violates retry transition semantics · case 04

Request reset violates retry transition semantics

HTTP retries◈ Members↗FA-30460

Retry routing with origin affinity: Request reset violates retry transition semantics · case 05

Request reset violates retry transition semantics

HTTP retries◈ Members↗FA-30461

Retry routing with origin affinity: Affinity capture violates retry transition semantics · case 01

Affinity capture violates retry transition semantics

HTTP retries● Open access↗FA-30462

Retry routing with origin affinity: Affinity capture violates retry transition semantics · case 02

Affinity capture violates retry transition semantics

HTTP retries◈ Members↗FA-30463

Retry routing with origin affinity: Affinity capture violates retry transition semantics · case 03

Affinity capture violates retry transition semantics

HTTP retries◈ Members↗FA-30464

Retry routing with origin affinity: Affinity capture violates retry transition semantics · case 04

Affinity capture violates retry transition semantics

HTTP retries◈ Members↗FA-30465

Retry routing with origin affinity: Affinity capture violates retry transition semantics · case 05

Affinity capture violates retry transition semantics

HTTP retries◈ Members↗FA-30466

Retry routing with origin affinity: Health down violates retry transition semantics · case 01

Health down violates retry transition semantics

HTTP retries● Open access↗FA-30467

Retry routing with origin affinity: Health down violates retry transition semantics · case 02

Health down violates retry transition semantics

HTTP retries◈ Members↗FA-30468

Retry routing with origin affinity: Health down violates retry transition semantics · case 03

Health down violates retry transition semantics

HTTP retries◈ Members↗FA-30469

Retry routing with origin affinity: Health down violates retry transition semantics · case 04

Health down violates retry transition semantics

HTTP retries◈ Members↗FA-30470

Retry routing with origin affinity: Health down violates retry transition semantics · case 05

Health down violates retry transition semantics

HTTP retries◈ Members↗FA-30471

Retry routing with origin affinity: Health up violates retry transition semantics · case 01

Health up violates retry transition semantics

HTTP retries● Open access↗FA-30472

Retry routing with origin affinity: Health up violates retry transition semantics · case 02

Health up violates retry transition semantics

HTTP retries◈ Members↗FA-30473

Retry routing with origin affinity: Health up violates retry transition semantics · case 03

Health up violates retry transition semantics

HTTP retries◈ Members↗FA-30474

Retry routing with origin affinity: Health up violates retry transition semantics · case 04

Health up violates retry transition semantics

HTTP retries◈ Members↗FA-30475

Retry routing with origin affinity: Health up violates retry transition semantics · case 05

Health up violates retry transition semantics

HTTP retries◈ Members↗FA-30476

Retry routing with origin affinity: Terminal pick violates retry transition semantics · case 01

Terminal pick violates retry transition semantics

HTTP retries● Open access↗FA-30477

Retry routing with origin affinity: Terminal pick violates retry transition semantics · case 02

Terminal pick violates retry transition semantics

HTTP retries◈ Members↗FA-30478

Retry routing with origin affinity: Terminal pick violates retry transition semantics · case 03

Terminal pick violates retry transition semantics

HTTP retries◈ Members↗FA-30479

Retry routing with origin affinity: Terminal pick violates retry transition semantics · case 04

Terminal pick violates retry transition semantics

HTTP retries◈ Members↗FA-30480

Retry routing with origin affinity: Terminal pick violates retry transition semantics · case 05

Terminal pick violates retry transition semantics

HTTP retries◈ Members↗FA-30481

Retry routing with origin affinity: Active pick violates retry transition semantics · case 01

Active pick violates retry transition semantics

HTTP retries● Open access↗FA-30482

Retry routing with origin affinity: Active pick violates retry transition semantics · case 02

Active pick violates retry transition semantics

HTTP retries◈ Members↗FA-30483

Retry routing with origin affinity: Active pick violates retry transition semantics · case 03

Active pick violates retry transition semantics

HTTP retries◈ Members↗FA-30484

Retry routing with origin affinity: Active pick violates retry transition semantics · case 04

Active pick violates retry transition semantics

HTTP retries◈ Members↗FA-30485

Retry routing with origin affinity: Active pick violates retry transition semantics · case 05

Active pick violates retry transition semantics

HTTP retries◈ Members↗FA-30486

Retry routing with origin affinity: Pin health violates retry transition semantics · case 01

Pin health violates retry transition semantics

HTTP retries● Open access↗FA-30487

Retry routing with origin affinity: Pin health violates retry transition semantics · case 02

Pin health violates retry transition semantics

HTTP retries◈ Members↗FA-30488

Retry routing with origin affinity: Pin health violates retry transition semantics · case 03

Pin health violates retry transition semantics

HTTP retries◈ Members↗FA-30489

Retry routing with origin affinity: Pin health violates retry transition semantics · case 04

Pin health violates retry transition semantics

HTTP retries◈ Members↗FA-30490

Retry routing with origin affinity: Pin health violates retry transition semantics · case 05

Pin health violates retry transition semantics

HTTP retries◈ Members↗FA-30491

Retry routing with origin affinity: Candidate health violates retry transition semantics · case 01

Candidate health violates retry transition semantics

HTTP retries● Open access↗FA-30492

Retry routing with origin affinity: Candidate health violates retry transition semantics · case 02

Candidate health violates retry transition semantics

HTTP retries◈ Members↗FA-30493

Retry routing with origin affinity: Candidate health violates retry transition semantics · case 03

Candidate health violates retry transition semantics

HTTP retries◈ Members↗FA-30494

Retry routing with origin affinity: Candidate health violates retry transition semantics · case 04

Candidate health violates retry transition semantics

HTTP retries◈ Members↗FA-30495

Retry routing with origin affinity: Candidate health violates retry transition semantics · case 05

Candidate health violates retry transition semantics

HTTP retries◈ Members↗FA-30496

Retry routing with origin affinity: Candidate first violates retry transition semantics · case 01

Candidate first violates retry transition semantics

HTTP retries● Open access↗FA-30497

Retry routing with origin affinity: Candidate first violates retry transition semantics · case 02

Candidate first violates retry transition semantics

HTTP retries◈ Members↗FA-30498

Retry routing with origin affinity: Candidate first violates retry transition semantics · case 03

Candidate first violates retry transition semantics

HTTP retries◈ Members↗FA-30499

Retry routing with origin affinity: Candidate first violates retry transition semantics · case 04

Candidate first violates retry transition semantics

HTTP retries◈ Members↗FA-30500

Retry routing with origin affinity: Candidate first violates retry transition semantics · case 05

Candidate first 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 ↗