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

One-shot request body replay refusal: A one-byte consumed body is admitted for replay · case 01

A one-byte consumed body is admitted for replay

HTTP retries● Open access↗
FA-29402

One-shot request body replay refusal: A one-byte consumed body is admitted for replay · case 02

A one-byte consumed body is admitted for replay

HTTP retries◈ Members↗
FA-29403

One-shot request body replay refusal: A one-byte consumed body is admitted for replay · case 03

A one-byte consumed body is admitted for replay

HTTP retries◈ Members↗
FA-29404

One-shot request body replay refusal: A one-byte consumed body is admitted for replay · case 04

A one-byte consumed body is admitted for replay

HTTP retries◈ Members↗
FA-29405

One-shot request body replay refusal: A one-byte consumed body is admitted for replay · case 05

A one-byte consumed body is admitted for replay

HTTP retries◈ Members↗
FA-29406

One-shot request body replay refusal: Opening a new body manufactures retry eligibility before a failure · case 01

Opening a new body manufactures retry eligibility before a failure

HTTP retries● Open access↗
FA-29407

One-shot request body replay refusal: Opening a new body manufactures retry eligibility before a failure · case 02

Opening a new body manufactures retry eligibility before a failure

HTTP retries◈ Members↗
FA-29408

One-shot request body replay refusal: Opening a new body manufactures retry eligibility before a failure · case 03

Opening a new body manufactures retry eligibility before a failure

HTTP retries◈ Members↗
FA-29409

One-shot request body replay refusal: Opening a new body manufactures retry eligibility before a failure · case 04

Opening a new body manufactures retry eligibility before a failure

HTTP retries◈ Members↗
FA-29410

One-shot request body replay refusal: Opening a new body manufactures retry eligibility before a failure · case 05

Opening a new body manufactures retry eligibility before a failure

HTTP retries◈ Members↗
FA-29411

One-shot request body replay refusal: Reopening after a completed transaction retains terminal state · case 01

Reopening after a completed transaction retains terminal state

HTTP retries● Open access↗
FA-29412

One-shot request body replay refusal: Reopening after a completed transaction retains terminal state · case 02

Reopening after a completed transaction retains terminal state

HTTP retries◈ Members↗
FA-29413

One-shot request body replay refusal: Reopening after a completed transaction retains terminal state · case 03

Reopening after a completed transaction retains terminal state

HTTP retries◈ Members↗
FA-29414

One-shot request body replay refusal: Reopening after a completed transaction retains terminal state · case 04

Reopening after a completed transaction retains terminal state

HTTP retries◈ Members↗
FA-29415

One-shot request body replay refusal: Reopening after a completed transaction retains terminal state · case 05

Reopening after a completed transaction retains terminal state

HTTP retries◈ Members↗
FA-29416

One-shot request body replay refusal: Known-unprocessed transport failures are dropped from retry state · case 01

Known-unprocessed transport failures are dropped from retry state

HTTP retries● Open access↗
FA-29417

One-shot request body replay refusal: Known-unprocessed transport failures are dropped from retry state · case 02

Known-unprocessed transport failures are dropped from retry state

HTTP retries◈ Members↗
FA-29418

One-shot request body replay refusal: Known-unprocessed transport failures are dropped from retry state · case 03

Known-unprocessed transport failures are dropped from retry state

HTTP retries◈ Members↗
FA-29419

One-shot request body replay refusal: Known-unprocessed transport failures are dropped from retry state · case 04

Known-unprocessed transport failures are dropped from retry state

HTTP retries◈ Members↗
FA-29420

One-shot request body replay refusal: Known-unprocessed transport failures are dropped from retry state · case 05

Known-unprocessed transport failures are dropped from retry state

HTTP retries◈ Members↗
FA-29421

One-shot request body replay refusal: Retry proceeds before a request body was opened · case 01

Retry proceeds before a request body was opened

HTTP retries● Open access↗
FA-29422

One-shot request body replay refusal: Retry proceeds before a request body was opened · case 02

Retry proceeds before a request body was opened

HTTP retries◈ Members↗
FA-29423

One-shot request body replay refusal: Retry proceeds before a request body was opened · case 03

Retry proceeds before a request body was opened

HTTP retries◈ Members↗
FA-29424

One-shot request body replay refusal: Retry proceeds before a request body was opened · case 04

Retry proceeds before a request body was opened

HTTP retries◈ Members↗
FA-29425

One-shot request body replay refusal: Retry proceeds before a request body was opened · case 05

Retry proceeds before a request body was opened

HTTP retries◈ Members↗
FA-29426

One-shot request body replay refusal: Repeated retry commands create attempts without another failure · case 01

Repeated retry commands create attempts without another failure

HTTP retries● Open access↗
FA-29427

One-shot request body replay refusal: Repeated retry commands create attempts without another failure · case 02

Repeated retry commands create attempts without another failure

HTTP retries◈ Members↗
FA-29428

One-shot request body replay refusal: Repeated retry commands create attempts without another failure · case 03

Repeated retry commands create attempts without another failure

HTTP retries◈ Members↗
FA-29429

One-shot request body replay refusal: Repeated retry commands create attempts without another failure · case 04

Repeated retry commands create attempts without another failure

HTTP retries◈ Members↗
FA-29430

One-shot request body replay refusal: Repeated retry commands create attempts without another failure · case 05

Repeated retry commands create attempts without another failure

HTTP retries◈ Members↗
FA-29431

One-shot request body replay refusal: A successful retry admission leaves its failure token reusable · case 01

A successful retry admission leaves its failure token reusable

HTTP retries● Open access↗
FA-29432

One-shot request body replay refusal: A successful retry admission leaves its failure token reusable · case 02

A successful retry admission leaves its failure token reusable

HTTP retries◈ Members↗
FA-29433

One-shot request body replay refusal: A successful retry admission leaves its failure token reusable · case 03

A successful retry admission leaves its failure token reusable

HTTP retries◈ Members↗
FA-29434

One-shot request body replay refusal: A successful retry admission leaves its failure token reusable · case 04

A successful retry admission leaves its failure token reusable

HTTP retries◈ Members↗
FA-29435

One-shot request body replay refusal: A successful retry admission leaves its failure token reusable · case 05

A successful retry admission leaves its failure token reusable

HTTP retries◈ Members↗
FA-29436

One-shot request body replay refusal: A successful empty upload permits another retry · case 01

A successful empty upload permits another retry

HTTP retries● Open access↗
FA-29437

One-shot request body replay refusal: A successful empty upload permits another retry · case 02

A successful empty upload permits another retry

HTTP retries◈ Members↗
FA-29438

One-shot request body replay refusal: A successful empty upload permits another retry · case 03

A successful empty upload permits another retry

HTTP retries◈ Members↗
FA-29439

One-shot request body replay refusal: A successful empty upload permits another retry · case 04

A successful empty upload permits another retry

HTTP retries◈ Members↗
FA-29440

One-shot request body replay refusal: A successful empty upload permits another retry · case 05

A successful empty upload permits another retry

HTTP retries◈ Members↗
FA-29441

Fresh body factories on retries: A retry factory observes a changed body recipe · case 01

A retry factory observes a changed body recipe

HTTP retries● Open access↗
FA-29442

Fresh body factories on retries: A retry factory observes a changed body recipe · case 02

A retry factory observes a changed body recipe

HTTP retries◈ Members↗
FA-29443

Fresh body factories on retries: A retry factory observes a changed body recipe · case 03

A retry factory observes a changed body recipe

HTTP retries◈ Members↗
FA-29444

Fresh body factories on retries: A retry factory observes a changed body recipe · case 04

A retry factory observes a changed body recipe

HTTP retries◈ Members↗
FA-29445

Fresh body factories on retries: A retry factory observes a changed body recipe · case 05

A retry factory observes a changed body recipe

HTTP retries◈ Members↗
FA-29446

Fresh body factories on retries: A new request inherits spent factory invocations · case 01

A new request inherits spent factory invocations

HTTP retries● Open access↗
FA-29447

Fresh body factories on retries: A new request inherits spent factory invocations · case 02

A new request inherits spent factory invocations

HTTP retries◈ Members↗
FA-29448

Fresh body factories on retries: A new request inherits spent factory invocations · case 03

A new request inherits spent factory invocations

HTTP retries◈ Members↗
FA-29449

Fresh body factories on retries: A new request inherits spent factory invocations · case 04

A new request inherits spent factory invocations

HTTP retries◈ Members↗
FA-29450

Fresh body factories on retries: A new request inherits spent factory invocations · case 05

A new request inherits spent factory invocations

HTTP retries◈ Members↗
FA-29451

Fresh body factories on retries: Opening a recipe exposes a stale previous body before invoking its factory · case 01

Opening a recipe exposes a stale previous body before invoking its factory

HTTP retries● Open access↗
FA-29452

Fresh body factories on retries: Opening a recipe exposes a stale previous body before invoking its factory · case 02

Opening a recipe exposes a stale previous body before invoking its factory

HTTP retries◈ Members↗
FA-29453

Fresh body factories on retries: Opening a recipe exposes a stale previous body before invoking its factory · case 03

Opening a recipe exposes a stale previous body before invoking its factory

HTTP retries◈ Members↗
FA-29454

Fresh body factories on retries: Opening a recipe exposes a stale previous body before invoking its factory · case 04

Opening a recipe exposes a stale previous body before invoking its factory

HTTP retries◈ Members↗
FA-29455

Fresh body factories on retries: Opening a recipe exposes a stale previous body before invoking its factory · case 05

Opening a recipe exposes a stale previous body before invoking its factory

HTTP retries◈ Members↗
FA-29456

Fresh body factories on retries: An exhausted factory is invoked one extra time · case 01

An exhausted factory is invoked one extra time

HTTP retries● Open access↗
FA-29457

Fresh body factories on retries: An exhausted factory is invoked one extra time · case 02

An exhausted factory is invoked one extra time

HTTP retries◈ Members↗
FA-29458

Fresh body factories on retries: An exhausted factory is invoked one extra time · case 03

An exhausted factory is invoked one extra time

HTTP retries◈ Members↗
FA-29459

Fresh body factories on retries: An exhausted factory is invoked one extra time · case 04

An exhausted factory is invoked one extra time

HTTP retries◈ Members↗
FA-29460

Fresh body factories on retries: An exhausted factory is invoked one extra time · case 05

An exhausted factory is invoked one extra time

HTTP retries◈ Members↗
FA-29461

Fresh body factories on retries: Retry builds the body from mutable current configuration · case 01

Retry builds the body from mutable current configuration

HTTP retries● Open access↗
FA-29462

Fresh body factories on retries: Retry builds the body from mutable current configuration · case 02

Retry builds the body from mutable current configuration

HTTP retries◈ Members↗
FA-29463

Fresh body factories on retries: Retry builds the body from mutable current configuration · case 03

Retry builds the body from mutable current configuration

HTTP retries◈ Members↗
FA-29464

Fresh body factories on retries: Retry builds the body from mutable current configuration · case 04

Retry builds the body from mutable current configuration

HTTP retries◈ Members↗
FA-29465

Fresh body factories on retries: Retry builds the body from mutable current configuration · case 05

Retry builds the body from mutable current configuration

HTTP retries◈ Members↗
FA-29466

Fresh body factories on retries: A fresh retry body inherits a consumed cursor · case 01

A fresh retry body inherits a consumed cursor

HTTP retries● Open access↗
FA-29467

Fresh body factories on retries: A fresh retry body inherits a consumed cursor · case 02

A fresh retry body inherits a consumed cursor

HTTP retries◈ Members↗
FA-29468

Fresh body factories on retries: A fresh retry body inherits a consumed cursor · case 03

A fresh retry body inherits a consumed cursor

HTTP retries◈ Members↗
FA-29469

Fresh body factories on retries: A fresh retry body inherits a consumed cursor · case 04

A fresh retry body inherits a consumed cursor

HTTP retries◈ Members↗
FA-29470

Fresh body factories on retries: A fresh retry body inherits a consumed cursor · case 05

A fresh retry body inherits a consumed cursor

HTTP retries◈ Members↗
FA-29471

Fresh body factories on retries: Factory calls fail to consume exactly one attempt allowance · case 01

Factory calls fail to consume exactly one attempt allowance

HTTP retries● Open access↗
FA-29472

Fresh body factories on retries: Factory calls fail to consume exactly one attempt allowance · case 02

Factory calls fail to consume exactly one attempt allowance

HTTP retries◈ Members↗
FA-29473

Fresh body factories on retries: Factory calls fail to consume exactly one attempt allowance · case 03

Factory calls fail to consume exactly one attempt allowance

HTTP retries◈ Members↗
FA-29474

Fresh body factories on retries: Factory calls fail to consume exactly one attempt allowance · case 04

Factory calls fail to consume exactly one attempt allowance

HTTP retries◈ Members↗
FA-29475

Fresh body factories on retries: Factory calls fail to consume exactly one attempt allowance · case 05

Factory calls fail to consume exactly one attempt allowance

HTTP retries◈ Members↗
FA-29476

Fresh body factories on retries: Empty retry bodies are incorrectly marked inactive · case 01

Empty retry bodies are incorrectly marked inactive

HTTP retries● Open access↗
FA-29477

Fresh body factories on retries: Empty retry bodies are incorrectly marked inactive · case 02

Empty retry bodies are incorrectly marked inactive

HTTP retries◈ Members↗
FA-29478

Fresh body factories on retries: Empty retry bodies are incorrectly marked inactive · case 03

Empty retry bodies are incorrectly marked inactive

HTTP retries◈ Members↗
FA-29479

Fresh body factories on retries: Empty retry bodies are incorrectly marked inactive · case 04

Empty retry bodies are incorrectly marked inactive

HTTP retries◈ Members↗
FA-29480

Fresh body factories on retries: Empty retry bodies are incorrectly marked inactive · case 05

Empty retry bodies are incorrectly marked inactive

HTTP retries◈ Members↗
FA-29481

Nested client retry ownership: Nested retry entry changes owner order or starts with a spent budget · case 01

Nested retry entry changes owner order or starts with a spent budget

HTTP retries● Open access↗
FA-29482

Nested client retry ownership: Nested retry entry changes owner order or starts with a spent budget · case 02

Nested retry entry changes owner order or starts with a spent budget

HTTP retries◈ Members↗
FA-29483

Nested client retry ownership: Nested retry entry changes owner order or starts with a spent budget · case 03

Nested retry entry changes owner order or starts with a spent budget

HTTP retries◈ Members↗
FA-29484

Nested client retry ownership: Nested retry entry changes owner order or starts with a spent budget · case 04

Nested retry entry changes owner order or starts with a spent budget

HTTP retries◈ Members↗
FA-29485

Nested client retry ownership: Nested retry entry changes owner order or starts with a spent budget · case 05

Nested retry entry changes owner order or starts with a spent budget

HTTP retries◈ Members↗
FA-29486

Nested client retry ownership: Leaving a child discards the parent retry owner · case 01

Leaving a child discards the parent retry owner

HTTP retries● Open access↗
FA-29487

Nested client retry ownership: Leaving a child discards the parent retry owner · case 02

Leaving a child discards the parent retry owner

HTTP retries◈ Members↗
FA-29488

Nested client retry ownership: Leaving a child discards the parent retry owner · case 03

Leaving a child discards the parent retry owner

HTTP retries◈ Members↗
FA-29489

Nested client retry ownership: Leaving a child discards the parent retry owner · case 04

Leaving a child discards the parent retry owner

HTTP retries◈ Members↗
FA-29490

Nested client retry ownership: Leaving a child discards the parent retry owner · case 05

Leaving a child discards the parent retry owner

HTTP retries◈ Members↗
FA-29491

Nested client retry ownership: Successful nested requests retain retry scopes · case 01

Successful nested requests retain retry scopes

HTTP retries● Open access↗
FA-29492

Nested client retry ownership: Successful nested requests retain retry scopes · case 02

Successful nested requests retain retry scopes

HTTP retries◈ Members↗
FA-29493

Nested client retry ownership: Successful nested requests retain retry scopes · case 03

Successful nested requests retain retry scopes

HTTP retries◈ Members↗
FA-29494

Nested client retry ownership: Successful nested requests retain retry scopes · case 04

Successful nested requests retain retry scopes

HTTP retries◈ Members↗
FA-29495

Nested client retry ownership: Successful nested requests retain retry scopes · case 05

Successful nested requests retain retry scopes

HTTP retries◈ Members↗
FA-29496

Nested client retry ownership: A single root retry scope is misclassified unowned · case 01

A single root retry scope is misclassified unowned

HTTP retries● Open access↗
FA-29497

Nested client retry ownership: A single root retry scope is misclassified unowned · case 02

A single root retry scope is misclassified unowned

HTTP retries◈ Members↗
FA-29498

Nested client retry ownership: A single root retry scope is misclassified unowned · case 03

A single root retry scope is misclassified unowned

HTTP retries◈ Members↗
FA-29499

Nested client retry ownership: A single root retry scope is misclassified unowned · case 04

A single root retry scope is misclassified unowned

HTTP retries◈ Members↗
FA-29500

Nested client retry ownership: A single root retry scope is misclassified unowned · case 05

A single root retry scope is misclassified unowned

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 ↗