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

Retry after consumer-visible response delivery: Zero-length callbacks erase or invent consumer-visible delivery · case 01

Zero-length callbacks erase or invent consumer-visible delivery

HTTP retries● Open access↗FA-29702

Retry after consumer-visible response delivery: Zero-length callbacks erase or invent consumer-visible delivery · case 02

Zero-length callbacks erase or invent consumer-visible delivery

HTTP retries◈ Members↗FA-29703

Retry after consumer-visible response delivery: Zero-length callbacks erase or invent consumer-visible delivery · case 03

Zero-length callbacks erase or invent consumer-visible delivery

HTTP retries◈ Members↗FA-29704

Retry after consumer-visible response delivery: Zero-length callbacks erase or invent consumer-visible delivery · case 04

Zero-length callbacks erase or invent consumer-visible delivery

HTTP retries◈ Members↗FA-29705

Retry after consumer-visible response delivery: Zero-length callbacks erase or invent consumer-visible delivery · case 05

Zero-length callbacks erase or invent consumer-visible delivery

HTTP retries◈ Members↗FA-29706

Retry after consumer-visible response delivery: Repeated failure callbacks authorize retries without an active attempt · case 01

Repeated failure callbacks authorize retries without an active attempt

HTTP retries● Open access↗FA-29707

Retry after consumer-visible response delivery: Repeated failure callbacks authorize retries without an active attempt · case 02

Repeated failure callbacks authorize retries without an active attempt

HTTP retries◈ Members↗FA-29708

Retry after consumer-visible response delivery: Repeated failure callbacks authorize retries without an active attempt · case 03

Repeated failure callbacks authorize retries without an active attempt

HTTP retries◈ Members↗FA-29709

Retry after consumer-visible response delivery: Repeated failure callbacks authorize retries without an active attempt · case 04

Repeated failure callbacks authorize retries without an active attempt

HTTP retries◈ Members↗FA-29710

Retry after consumer-visible response delivery: Repeated failure callbacks authorize retries without an active attempt · case 05

Repeated failure callbacks authorize retries without an active attempt

HTTP retries◈ Members↗FA-29711

Retry after consumer-visible response delivery: Failure leaves the response attempt active for duplicate retry admission · case 01

Failure leaves the response attempt active for duplicate retry admission

HTTP retries● Open access↗FA-29712

Retry after consumer-visible response delivery: Failure leaves the response attempt active for duplicate retry admission · case 02

Failure leaves the response attempt active for duplicate retry admission

HTTP retries◈ Members↗FA-29713

Retry after consumer-visible response delivery: Failure leaves the response attempt active for duplicate retry admission · case 03

Failure leaves the response attempt active for duplicate retry admission

HTTP retries◈ Members↗FA-29714

Retry after consumer-visible response delivery: Failure leaves the response attempt active for duplicate retry admission · case 04

Failure leaves the response attempt active for duplicate retry admission

HTTP retries◈ Members↗FA-29715

Retry after consumer-visible response delivery: Failure leaves the response attempt active for duplicate retry admission · case 05

Failure leaves the response attempt active for duplicate retry admission

HTTP retries◈ Members↗FA-29716

Retry after consumer-visible response delivery: Retry suppression mishandles one-byte or empty consumer delivery · case 01

Retry suppression mishandles one-byte or empty consumer delivery

HTTP retries● Open access↗FA-29717

Retry after consumer-visible response delivery: Retry suppression mishandles one-byte or empty consumer delivery · case 02

Retry suppression mishandles one-byte or empty consumer delivery

HTTP retries◈ Members↗FA-29718

Retry after consumer-visible response delivery: Retry suppression mishandles one-byte or empty consumer delivery · case 03

Retry suppression mishandles one-byte or empty consumer delivery

HTTP retries◈ Members↗FA-29719

Retry after consumer-visible response delivery: Retry suppression mishandles one-byte or empty consumer delivery · case 04

Retry suppression mishandles one-byte or empty consumer delivery

HTTP retries◈ Members↗FA-29720

Retry after consumer-visible response delivery: Retry suppression mishandles one-byte or empty consumer delivery · case 05

Retry suppression mishandles one-byte or empty consumer delivery

HTTP retries◈ Members↗FA-29721

Retry after consumer-visible response delivery: A partially exposed response is not terminally sealed · case 01

A partially exposed response is not terminally sealed

HTTP retries● Open access↗FA-29722

Retry after consumer-visible response delivery: A partially exposed response is not terminally sealed · case 02

A partially exposed response is not terminally sealed

HTTP retries◈ Members↗FA-29723

Retry after consumer-visible response delivery: A partially exposed response is not terminally sealed · case 03

A partially exposed response is not terminally sealed

HTTP retries◈ Members↗FA-29724

Retry after consumer-visible response delivery: A partially exposed response is not terminally sealed · case 04

A partially exposed response is not terminally sealed

HTTP retries◈ Members↗FA-29725

Retry after consumer-visible response delivery: A partially exposed response is not terminally sealed · case 05

A partially exposed response is not terminally sealed

HTTP retries◈ Members↗FA-29726

Retry after consumer-visible response delivery: Completing an empty response does not stop later attempts · case 01

Completing an empty response does not stop later attempts

HTTP retries● Open access↗FA-29727

Retry after consumer-visible response delivery: Completing an empty response does not stop later attempts · case 02

Completing an empty response does not stop later attempts

HTTP retries◈ Members↗FA-29728

Retry after consumer-visible response delivery: Completing an empty response does not stop later attempts · case 03

Completing an empty response does not stop later attempts

HTTP retries◈ Members↗FA-29729

Retry after consumer-visible response delivery: Completing an empty response does not stop later attempts · case 04

Completing an empty response does not stop later attempts

HTTP retries◈ Members↗FA-29730

Retry after consumer-visible response delivery: Completing an empty response does not stop later attempts · case 05

Completing an empty response does not stop later attempts

HTTP retries◈ Members↗FA-29731

GOAWAY retry admission: Block draining violates retry transition semantics · case 01

Block draining violates retry transition semantics

HTTP retries● Open access↗FA-29732

GOAWAY retry admission: Block draining violates retry transition semantics · case 02

Block draining violates retry transition semantics

HTTP retries◈ Members↗FA-29733

GOAWAY retry admission: Block draining violates retry transition semantics · case 03

Block draining violates retry transition semantics

HTTP retries◈ Members↗FA-29734

GOAWAY retry admission: Block draining violates retry transition semantics · case 04

Block draining violates retry transition semantics

HTTP retries◈ Members↗FA-29735

GOAWAY retry admission: Block draining violates retry transition semantics · case 05

Block draining violates retry transition semantics

HTTP retries◈ Members↗FA-29736

GOAWAY retry admission: Stream identity violates retry transition semantics · case 01

Stream identity violates retry transition semantics

HTTP retries● Open access↗FA-29737

GOAWAY retry admission: Stream identity violates retry transition semantics · case 02

Stream identity violates retry transition semantics

HTTP retries◈ Members↗FA-29738

GOAWAY retry admission: Stream identity violates retry transition semantics · case 03

Stream identity violates retry transition semantics

HTTP retries◈ Members↗FA-29739

GOAWAY retry admission: Stream identity violates retry transition semantics · case 04

Stream identity violates retry transition semantics

HTTP retries◈ Members↗FA-29740

GOAWAY retry admission: Stream identity violates retry transition semantics · case 05

Stream identity violates retry transition semantics

HTTP retries◈ Members↗FA-29741

GOAWAY retry admission: Initial active violates retry transition semantics · case 01

Initial active violates retry transition semantics

HTTP retries● Open access↗FA-29742

GOAWAY retry admission: Initial active violates retry transition semantics · case 02

Initial active violates retry transition semantics

HTTP retries◈ Members↗FA-29743

GOAWAY retry admission: Initial active violates retry transition semantics · case 03

Initial active violates retry transition semantics

HTTP retries◈ Members↗FA-29744

GOAWAY retry admission: Initial active violates retry transition semantics · case 04

Initial active violates retry transition semantics

HTTP retries◈ Members↗FA-29745

GOAWAY retry admission: Initial active violates retry transition semantics · case 05

Initial active violates retry transition semantics

HTTP retries◈ Members↗FA-29746

GOAWAY retry admission: Goaway min violates retry transition semantics · case 01

Goaway min violates retry transition semantics

HTTP retries● Open access↗FA-29747

GOAWAY retry admission: Goaway min violates retry transition semantics · case 02

Goaway min violates retry transition semantics

HTTP retries◈ Members↗FA-29748

GOAWAY retry admission: Goaway min violates retry transition semantics · case 03

Goaway min violates retry transition semantics

HTTP retries◈ Members↗FA-29749

GOAWAY retry admission: Goaway min violates retry transition semantics · case 04

Goaway min violates retry transition semantics

HTTP retries◈ Members↗FA-29750

GOAWAY retry admission: Goaway min violates retry transition semantics · case 05

Goaway min violates retry transition semantics

HTTP retries◈ Members↗FA-29751

GOAWAY retry admission: First boundary violates retry transition semantics · case 01

First boundary violates retry transition semantics

HTTP retries● Open access↗FA-29752

GOAWAY retry admission: First boundary violates retry transition semantics · case 02

First boundary violates retry transition semantics

HTTP retries◈ Members↗FA-29753

GOAWAY retry admission: First boundary violates retry transition semantics · case 03

First boundary violates retry transition semantics

HTTP retries◈ Members↗FA-29754

GOAWAY retry admission: First boundary violates retry transition semantics · case 04

First boundary violates retry transition semantics

HTTP retries◈ Members↗FA-29755

GOAWAY retry admission: First boundary violates retry transition semantics · case 05

First boundary violates retry transition semantics

HTTP retries◈ Members↗FA-29756

GOAWAY retry admission: Success closes violates retry transition semantics · case 01

Success closes violates retry transition semantics

HTTP retries● Open access↗FA-29757

GOAWAY retry admission: Success closes violates retry transition semantics · case 02

Success closes violates retry transition semantics

HTTP retries◈ Members↗FA-29758

GOAWAY retry admission: Success closes violates retry transition semantics · case 03

Success closes violates retry transition semantics

HTTP retries◈ Members↗FA-29759

GOAWAY retry admission: Success closes violates retry transition semantics · case 04

Success closes violates retry transition semantics

HTTP retries◈ Members↗FA-29760

GOAWAY retry admission: Success closes violates retry transition semantics · case 05

Success closes violates retry transition semantics

HTTP retries◈ Members↗FA-29761

GOAWAY retry admission: Unknown result violates retry transition semantics · case 01

Unknown result violates retry transition semantics

HTTP retries● Open access↗FA-29762

GOAWAY retry admission: Unknown result violates retry transition semantics · case 02

Unknown result violates retry transition semantics

HTTP retries◈ Members↗FA-29763

GOAWAY retry admission: Unknown result violates retry transition semantics · case 03

Unknown result violates retry transition semantics

HTTP retries◈ Members↗FA-29764

GOAWAY retry admission: Unknown result violates retry transition semantics · case 04

Unknown result violates retry transition semantics

HTTP retries◈ Members↗FA-29765

GOAWAY retry admission: Unknown result violates retry transition semantics · case 05

Unknown result violates retry transition semantics

HTTP retries◈ Members↗FA-29766

GOAWAY retry admission: Finished result violates retry transition semantics · case 01

Finished result violates retry transition semantics

HTTP retries● Open access↗FA-29767

GOAWAY retry admission: Finished result violates retry transition semantics · case 02

Finished result violates retry transition semantics

HTTP retries◈ Members↗FA-29768

GOAWAY retry admission: Finished result violates retry transition semantics · case 03

Finished result violates retry transition semantics

HTTP retries◈ Members↗FA-29769

GOAWAY retry admission: Finished result violates retry transition semantics · case 04

Finished result violates retry transition semantics

HTTP retries◈ Members↗FA-29770

GOAWAY retry admission: Finished result violates retry transition semantics · case 05

Finished result violates retry transition semantics

HTTP retries◈ Members↗FA-29771

GOAWAY retry admission: Consume failure violates retry transition semantics · case 01

Consume failure violates retry transition semantics

HTTP retries● Open access↗FA-29772

GOAWAY retry admission: Consume failure violates retry transition semantics · case 02

Consume failure violates retry transition semantics

HTTP retries◈ Members↗FA-29773

GOAWAY retry admission: Consume failure violates retry transition semantics · case 03

Consume failure violates retry transition semantics

HTTP retries◈ Members↗FA-29774

GOAWAY retry admission: Consume failure violates retry transition semantics · case 04

Consume failure violates retry transition semantics

HTTP retries◈ Members↗FA-29775

GOAWAY retry admission: Consume failure violates retry transition semantics · case 05

Consume failure violates retry transition semantics

HTTP retries◈ Members↗FA-29776

GOAWAY retry admission: Processed boundary violates retry transition semantics · case 01

Processed boundary violates retry transition semantics

HTTP retries● Open access↗FA-29777

GOAWAY retry admission: Processed boundary violates retry transition semantics · case 02

Processed boundary violates retry transition semantics

HTTP retries◈ Members↗FA-29778

GOAWAY retry admission: Processed boundary violates retry transition semantics · case 03

Processed boundary violates retry transition semantics

HTTP retries◈ Members↗FA-29779

GOAWAY retry admission: Processed boundary violates retry transition semantics · case 04

Processed boundary violates retry transition semantics

HTTP retries◈ Members↗FA-29780

GOAWAY retry admission: Processed boundary violates retry transition semantics · case 05

Processed boundary violates retry transition semantics

HTTP retries◈ Members↗FA-29781

GOAWAY retry admission: Body replay violates retry transition semantics · case 01

Body replay violates retry transition semantics

HTTP retries● Open access↗FA-29782

GOAWAY retry admission: Body replay violates retry transition semantics · case 02

Body replay violates retry transition semantics

HTTP retries◈ Members↗FA-29783

GOAWAY retry admission: Body replay violates retry transition semantics · case 03

Body replay violates retry transition semantics

HTTP retries◈ Members↗FA-29784

GOAWAY retry admission: Body replay violates retry transition semantics · case 04

Body replay violates retry transition semantics

HTTP retries◈ Members↗FA-29785

GOAWAY retry admission: Body replay violates retry transition semantics · case 05

Body replay violates retry transition semantics

HTTP retries◈ Members↗FA-29786

GOAWAY retry admission: Ambiguous processing violates retry transition semantics · case 01

Ambiguous processing violates retry transition semantics

HTTP retries● Open access↗FA-29787

GOAWAY retry admission: Ambiguous processing violates retry transition semantics · case 02

Ambiguous processing violates retry transition semantics

HTTP retries◈ Members↗FA-29788

GOAWAY retry admission: Ambiguous processing violates retry transition semantics · case 03

Ambiguous processing violates retry transition semantics

HTTP retries◈ Members↗FA-29789

GOAWAY retry admission: Ambiguous processing violates retry transition semantics · case 04

Ambiguous processing violates retry transition semantics

HTTP retries◈ Members↗FA-29790

GOAWAY retry admission: Ambiguous processing violates retry transition semantics · case 05

Ambiguous processing violates retry transition semantics

HTTP retries◈ Members↗FA-29791

GOAWAY retry admission: Reconnect boundary violates retry transition semantics · case 01

Reconnect boundary violates retry transition semantics

HTTP retries● Open access↗FA-29792

GOAWAY retry admission: Reconnect boundary violates retry transition semantics · case 02

Reconnect boundary violates retry transition semantics

HTTP retries◈ Members↗FA-29793

GOAWAY retry admission: Reconnect boundary violates retry transition semantics · case 03

Reconnect boundary violates retry transition semantics

HTTP retries◈ Members↗FA-29794

GOAWAY retry admission: Reconnect boundary violates retry transition semantics · case 04

Reconnect boundary violates retry transition semantics

HTTP retries◈ Members↗FA-29795

GOAWAY retry admission: Reconnect boundary violates retry transition semantics · case 05

Reconnect boundary violates retry transition semantics

HTTP retries◈ Members↗FA-29796

GOAWAY retry admission: Reconnect streams violates retry transition semantics · case 01

Reconnect streams violates retry transition semantics

HTTP retries● Open access↗FA-29797

GOAWAY retry admission: Reconnect streams violates retry transition semantics · case 02

Reconnect streams violates retry transition semantics

HTTP retries◈ Members↗FA-29798

GOAWAY retry admission: Reconnect streams violates retry transition semantics · case 03

Reconnect streams violates retry transition semantics

HTTP retries◈ Members↗FA-29799

GOAWAY retry admission: Reconnect streams violates retry transition semantics · case 04

Reconnect streams violates retry transition semantics

HTTP retries◈ Members↗FA-29800

GOAWAY retry admission: Reconnect streams violates retry transition semantics · case 05

Reconnect streams 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 ↗