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

An encoded partial response carries its own representation validator · case 01

An encoded partial response carries its own representation validator.

HTTP ranges● Open access↗
FA-26402

An encoded partial response carries its own representation validator · case 02

An encoded partial response carries its own representation validator.

HTTP ranges◈ Members↗
FA-26403

An encoded partial response carries its own representation validator · case 03

An encoded partial response carries its own representation validator.

HTTP ranges◈ Members↗
FA-26404

An encoded partial response carries its own representation validator · case 04

An encoded partial response carries its own representation validator.

HTTP ranges◈ Members↗
FA-26405

An encoded partial response carries its own representation validator · case 05

An encoded partial response carries its own representation validator.

HTTP ranges◈ Members↗
FA-26406

Explicit identity exclusion prevents uncompressed range fallback · case 01

Explicit identity exclusion prevents uncompressed range fallback.

HTTP ranges● Open access↗
FA-26407

Explicit identity exclusion prevents uncompressed range fallback · case 02

Explicit identity exclusion prevents uncompressed range fallback.

HTTP ranges◈ Members↗
FA-26408

Explicit identity exclusion prevents uncompressed range fallback · case 03

Explicit identity exclusion prevents uncompressed range fallback.

HTTP ranges◈ Members↗
FA-26409

Explicit identity exclusion prevents uncompressed range fallback · case 04

Explicit identity exclusion prevents uncompressed range fallback.

HTTP ranges◈ Members↗
FA-26410

Explicit identity exclusion prevents uncompressed range fallback · case 05

Explicit identity exclusion prevents uncompressed range fallback.

HTTP ranges◈ Members↗
FA-26411

Range negotiation preserves preexisting Vary dimensions · case 01

Range negotiation preserves preexisting Vary dimensions.

HTTP ranges● Open access↗
FA-26412

Range negotiation preserves preexisting Vary dimensions · case 02

Range negotiation preserves preexisting Vary dimensions.

HTTP ranges◈ Members↗
FA-26413

Range negotiation preserves preexisting Vary dimensions · case 03

Range negotiation preserves preexisting Vary dimensions.

HTTP ranges◈ Members↗
FA-26414

Range negotiation preserves preexisting Vary dimensions · case 04

Range negotiation preserves preexisting Vary dimensions.

HTTP ranges◈ Members↗
FA-26415

Range negotiation preserves preexisting Vary dimensions · case 05

Range negotiation preserves preexisting Vary dimensions.

HTTP ranges◈ Members↗
FA-26416

Accept-Ranges reflects the chosen representation source capability · case 01

Accept-Ranges reflects the chosen representation source capability.

HTTP ranges● Open access↗
FA-26417

Accept-Ranges reflects the chosen representation source capability · case 02

Accept-Ranges reflects the chosen representation source capability.

HTTP ranges◈ Members↗
FA-26418

Accept-Ranges reflects the chosen representation source capability · case 03

Accept-Ranges reflects the chosen representation source capability.

HTTP ranges◈ Members↗
FA-26419

Accept-Ranges reflects the chosen representation source capability · case 04

Accept-Ranges reflects the chosen representation source capability.

HTTP ranges◈ Members↗
FA-26420

Accept-Ranges reflects the chosen representation source capability · case 05

Accept-Ranges reflects the chosen representation source capability.

HTTP ranges◈ Members↗
FA-26421

A range read is rejected if metadata and body revisions diverge · case 01

A range read is rejected if metadata and body revisions diverge.

HTTP ranges● Open access↗
FA-26422

A range read is rejected if metadata and body revisions diverge · case 02

A range read is rejected if metadata and body revisions diverge.

HTTP ranges◈ Members↗
FA-26423

A range read is rejected if metadata and body revisions diverge · case 03

A range read is rejected if metadata and body revisions diverge.

HTTP ranges◈ Members↗
FA-26424

A range read is rejected if metadata and body revisions diverge · case 04

A range read is rejected if metadata and body revisions diverge.

HTTP ranges◈ Members↗
FA-26425

A range read is rejected if metadata and body revisions diverge · case 05

A range read is rejected if metadata and body revisions diverge.

HTTP ranges◈ Members↗
FA-26426

Partial cache entries distinguish selected language variants · case 01

Partial cache entries distinguish selected language variants.

HTTP ranges● Open access↗
FA-26427

Partial cache entries distinguish selected language variants · case 02

Partial cache entries distinguish selected language variants.

HTTP ranges◈ Members↗
FA-26428

Partial cache entries distinguish selected language variants · case 03

Partial cache entries distinguish selected language variants.

HTTP ranges◈ Members↗
FA-26429

Partial cache entries distinguish selected language variants · case 04

Partial cache entries distinguish selected language variants.

HTTP ranges◈ Members↗
FA-26430

Partial cache entries distinguish selected language variants · case 05

Partial cache entries distinguish selected language variants.

HTTP ranges◈ Members↗
FA-26431

Body rewriting removes source validators from range responses · case 01

Body rewriting removes source validators from range responses.

HTTP ranges● Open access↗
FA-26432

Body rewriting removes source validators from range responses · case 02

Body rewriting removes source validators from range responses.

HTTP ranges◈ Members↗
FA-26433

Body rewriting removes source validators from range responses · case 03

Body rewriting removes source validators from range responses.

HTTP ranges◈ Members↗
FA-26434

Body rewriting removes source validators from range responses · case 04

Body rewriting removes source validators from range responses.

HTTP ranges◈ Members↗
FA-26435

Body rewriting removes source validators from range responses · case 05

Body rewriting removes source validators from range responses.

HTTP ranges◈ Members↗
FA-26436

Unauthorized range probes hide whether the object exists · case 01

Unauthorized range probes hide whether the object exists.

HTTP ranges● Open access↗
FA-26437

Unauthorized range probes hide whether the object exists · case 02

Unauthorized range probes hide whether the object exists.

HTTP ranges◈ Members↗
FA-26438

Unauthorized range probes hide whether the object exists · case 03

Unauthorized range probes hide whether the object exists.

HTTP ranges◈ Members↗
FA-26439

Unauthorized range probes hide whether the object exists · case 04

Unauthorized range probes hide whether the object exists.

HTTP ranges◈ Members↗
FA-26440

Unauthorized range probes hide whether the object exists · case 05

Unauthorized range probes hide whether the object exists.

HTTP ranges◈ Members↗
FA-26441

Multipart delimiters cannot occur at payload line boundaries · case 01

Multipart delimiters cannot occur at payload line boundaries.

HTTP ranges● Open access↗
FA-26442

Multipart delimiters cannot occur at payload line boundaries · case 02

Multipart delimiters cannot occur at payload line boundaries.

HTTP ranges◈ Members↗
FA-26443

Multipart delimiters cannot occur at payload line boundaries · case 03

Multipart delimiters cannot occur at payload line boundaries.

HTTP ranges◈ Members↗
FA-26444

Multipart delimiters cannot occur at payload line boundaries · case 04

Multipart delimiters cannot occur at payload line boundaries.

HTTP ranges◈ Members↗
FA-26445

Multipart delimiters cannot occur at payload line boundaries · case 05

Multipart delimiters cannot occur at payload line boundaries.

HTTP ranges◈ Members↗
FA-26446

The multipart terminator closes the boundary exactly once · case 01

The multipart terminator closes the boundary exactly once.

HTTP ranges● Open access↗
FA-26447

The multipart terminator closes the boundary exactly once · case 02

The multipart terminator closes the boundary exactly once.

HTTP ranges◈ Members↗
FA-26448

The multipart terminator closes the boundary exactly once · case 03

The multipart terminator closes the boundary exactly once.

HTTP ranges◈ Members↗
FA-26449

The multipart terminator closes the boundary exactly once · case 04

The multipart terminator closes the boundary exactly once.

HTTP ranges◈ Members↗
FA-26450

The multipart terminator closes the boundary exactly once · case 05

The multipart terminator closes the boundary exactly once.

HTTP ranges◈ Members↗
FA-26451

Part payloads always precede a framing CRLF · case 01

Part payloads always precede a framing CRLF.

HTTP ranges● Open access↗
FA-26452

Part payloads always precede a framing CRLF · case 02

Part payloads always precede a framing CRLF.

HTTP ranges◈ Members↗
FA-26453

Part payloads always precede a framing CRLF · case 03

Part payloads always precede a framing CRLF.

HTTP ranges◈ Members↗
FA-26454

Part payloads always precede a framing CRLF · case 04

Part payloads always precede a framing CRLF.

HTTP ranges◈ Members↗
FA-26455

Part payloads always precede a framing CRLF · case 05

Part payloads always precede a framing CRLF.

HTTP ranges◈ Members↗
FA-26456

Multipart response type carries a boundary rather than the object media type · case 01

Multipart response type carries a boundary rather than the object media type.

HTTP ranges● Open access↗
FA-26457

Multipart response type carries a boundary rather than the object media type · case 02

Multipart response type carries a boundary rather than the object media type.

HTTP ranges◈ Members↗
FA-26458

Multipart response type carries a boundary rather than the object media type · case 03

Multipart response type carries a boundary rather than the object media type.

HTTP ranges◈ Members↗
FA-26459

Multipart response type carries a boundary rather than the object media type · case 04

Multipart response type carries a boundary rather than the object media type.

HTTP ranges◈ Members↗
FA-26460

Multipart response type carries a boundary rather than the object media type · case 05

Multipart response type carries a boundary rather than the object media type.

HTTP ranges◈ Members↗
FA-26461

Every part uses the selected representation media type · case 01

Every part uses the selected representation media type.

HTTP ranges● Open access↗
FA-26462

Every part uses the selected representation media type · case 02

Every part uses the selected representation media type.

HTTP ranges◈ Members↗
FA-26463

Every part uses the selected representation media type · case 03

Every part uses the selected representation media type.

HTTP ranges◈ Members↗
FA-26464

Every part uses the selected representation media type · case 04

Every part uses the selected representation media type.

HTTP ranges◈ Members↗
FA-26465

Every part uses the selected representation media type · case 05

Every part uses the selected representation media type.

HTTP ranges◈ Members↗
FA-26466

Multipart Content-Length includes headers and closing bytes · case 01

Multipart Content-Length includes headers and closing bytes.

HTTP ranges● Open access↗
FA-26467

Multipart Content-Length includes headers and closing bytes · case 02

Multipart Content-Length includes headers and closing bytes.

HTTP ranges◈ Members↗
FA-26468

Multipart Content-Length includes headers and closing bytes · case 03

Multipart Content-Length includes headers and closing bytes.

HTTP ranges◈ Members↗
FA-26469

Multipart Content-Length includes headers and closing bytes · case 04

Multipart Content-Length includes headers and closing bytes.

HTTP ranges◈ Members↗
FA-26470

Multipart Content-Length includes headers and closing bytes · case 05

Multipart Content-Length includes headers and closing bytes.

HTTP ranges◈ Members↗
FA-26471

Top-level range metadata is absent for multipart bodies · case 01

Top-level range metadata is absent for multipart bodies.

HTTP ranges● Open access↗
FA-26472

Top-level range metadata is absent for multipart bodies · case 02

Top-level range metadata is absent for multipart bodies.

HTTP ranges◈ Members↗
FA-26473

Top-level range metadata is absent for multipart bodies · case 03

Top-level range metadata is absent for multipart bodies.

HTTP ranges◈ Members↗
FA-26474

Top-level range metadata is absent for multipart bodies · case 04

Top-level range metadata is absent for multipart bodies.

HTTP ranges◈ Members↗
FA-26475

Top-level range metadata is absent for multipart bodies · case 05

Top-level range metadata is absent for multipart bodies.

HTTP ranges◈ Members↗
FA-26476

Multipart assembly preserves the normalized request order · case 01

Multipart assembly preserves the normalized request order.

HTTP ranges● Open access↗
FA-26477

Multipart assembly preserves the normalized request order · case 02

Multipart assembly preserves the normalized request order.

HTTP ranges◈ Members↗
FA-26478

Multipart assembly preserves the normalized request order · case 03

Multipart assembly preserves the normalized request order.

HTTP ranges◈ Members↗
FA-26479

Multipart assembly preserves the normalized request order · case 04

Multipart assembly preserves the normalized request order.

HTTP ranges◈ Members↗
FA-26480

Multipart assembly preserves the normalized request order · case 05

Multipart assembly preserves the normalized request order.

HTTP ranges◈ Members↗
FA-26481

A short part read prevents emission of a successful closing delimiter · case 01

A short part read prevents emission of a successful closing delimiter.

HTTP ranges● Open access↗
FA-26482

A short part read prevents emission of a successful closing delimiter · case 02

A short part read prevents emission of a successful closing delimiter.

HTTP ranges◈ Members↗
FA-26483

A short part read prevents emission of a successful closing delimiter · case 03

A short part read prevents emission of a successful closing delimiter.

HTTP ranges◈ Members↗
FA-26484

A short part read prevents emission of a successful closing delimiter · case 04

A short part read prevents emission of a successful closing delimiter.

HTTP ranges◈ Members↗
FA-26485

A short part read prevents emission of a successful closing delimiter · case 05

A short part read prevents emission of a successful closing delimiter.

HTTP ranges◈ Members↗
FA-26486

Part media types cannot insert extra framing lines · case 01

Part media types cannot insert extra framing lines.

HTTP ranges● Open access↗
FA-26487

Part media types cannot insert extra framing lines · case 02

Part media types cannot insert extra framing lines.

HTTP ranges◈ Members↗
FA-26488

Part media types cannot insert extra framing lines · case 03

Part media types cannot insert extra framing lines.

HTTP ranges◈ Members↗
FA-26489

Part media types cannot insert extra framing lines · case 04

Part media types cannot insert extra framing lines.

HTTP ranges◈ Members↗
FA-26490

Part media types cannot insert extra framing lines · case 05

Part media types cannot insert extra framing lines.

HTTP ranges◈ Members↗
FA-26491

Cached fragments with different validators cannot be joined · case 01

Cached fragments with different validators cannot be joined.

HTTP ranges● Open access↗
FA-26492

Cached fragments with different validators cannot be joined · case 02

Cached fragments with different validators cannot be joined.

HTTP ranges◈ Members↗
FA-26493

Cached fragments with different validators cannot be joined · case 03

Cached fragments with different validators cannot be joined.

HTTP ranges◈ Members↗
FA-26494

Cached fragments with different validators cannot be joined · case 04

Cached fragments with different validators cannot be joined.

HTTP ranges◈ Members↗
FA-26495

Cached fragments with different validators cannot be joined · case 05

Cached fragments with different validators cannot be joined.

HTTP ranges◈ Members↗
FA-26496

Overlapping fragments must agree on their bytes · case 01

Overlapping fragments must agree on their bytes.

HTTP ranges● Open access↗
FA-26497

Overlapping fragments must agree on their bytes · case 02

Overlapping fragments must agree on their bytes.

HTTP ranges◈ Members↗
FA-26498

Overlapping fragments must agree on their bytes · case 03

Overlapping fragments must agree on their bytes.

HTTP ranges◈ Members↗
FA-26499

Overlapping fragments must agree on their bytes · case 04

Overlapping fragments must agree on their bytes.

HTTP ranges◈ Members↗
FA-26500

Overlapping fragments must agree on their bytes · case 05

Overlapping fragments must agree on their bytes.

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