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

Each multipart range begins with its own absolute seek · case 01

Each multipart range begins with its own absolute seek.

HTTP ranges● Open access↗
FA-26602

Each multipart range begins with its own absolute seek · case 02

Each multipart range begins with its own absolute seek.

HTTP ranges◈ Members↗
FA-26603

Each multipart range begins with its own absolute seek · case 03

Each multipart range begins with its own absolute seek.

HTTP ranges◈ Members↗
FA-26604

Each multipart range begins with its own absolute seek · case 04

Each multipart range begins with its own absolute seek.

HTTP ranges◈ Members↗
FA-26605

Each multipart range begins with its own absolute seek · case 05

Each multipart range begins with its own absolute seek.

HTTP ranges◈ Members↗
FA-26606

Failed absolute seek prevents a range read from the stale cursor · case 01

Failed absolute seek prevents a range read from the stale cursor.

HTTP ranges● Open access↗
FA-26607

Failed absolute seek prevents a range read from the stale cursor · case 02

Failed absolute seek prevents a range read from the stale cursor.

HTTP ranges◈ Members↗
FA-26608

Failed absolute seek prevents a range read from the stale cursor · case 03

Failed absolute seek prevents a range read from the stale cursor.

HTTP ranges◈ Members↗
FA-26609

Failed absolute seek prevents a range read from the stale cursor · case 04

Failed absolute seek prevents a range read from the stale cursor.

HTTP ranges◈ Members↗
FA-26610

Failed absolute seek prevents a range read from the stale cursor · case 05

Failed absolute seek prevents a range read from the stale cursor.

HTTP ranges◈ Members↗
FA-26611

Download accounting counts accepted payload bytes instead of attempted bytes · case 01

Download accounting counts accepted payload bytes instead of attempted bytes.

HTTP ranges● Open access↗
FA-26612

Download accounting counts accepted payload bytes instead of attempted bytes · case 02

Download accounting counts accepted payload bytes instead of attempted bytes.

HTTP ranges◈ Members↗
FA-26613

Download accounting counts accepted payload bytes instead of attempted bytes · case 03

Download accounting counts accepted payload bytes instead of attempted bytes.

HTTP ranges◈ Members↗
FA-26614

Download accounting counts accepted payload bytes instead of attempted bytes · case 04

Download accounting counts accepted payload bytes instead of attempted bytes.

HTTP ranges◈ Members↗
FA-26615

Download accounting counts accepted payload bytes instead of attempted bytes · case 05

Download accounting counts accepted payload bytes instead of attempted bytes.

HTTP ranges◈ Members↗
FA-26616

Queued partial payloads preserve FIFO order under backpressure · case 01

Queued partial payloads preserve FIFO order under backpressure.

HTTP ranges● Open access↗
FA-26617

Queued partial payloads preserve FIFO order under backpressure · case 02

Queued partial payloads preserve FIFO order under backpressure.

HTTP ranges◈ Members↗
FA-26618

Queued partial payloads preserve FIFO order under backpressure · case 03

Queued partial payloads preserve FIFO order under backpressure.

HTTP ranges◈ Members↗
FA-26619

Queued partial payloads preserve FIFO order under backpressure · case 04

Queued partial payloads preserve FIFO order under backpressure.

HTTP ranges◈ Members↗
FA-26620

Queued partial payloads preserve FIFO order under backpressure · case 05

Queued partial payloads preserve FIFO order under backpressure.

HTTP ranges◈ Members↗
FA-26621

Range stream idle deadlines advance only on actual byte progress · case 01

Range stream idle deadlines advance only on actual byte progress.

HTTP ranges● Open access↗
FA-26622

Range stream idle deadlines advance only on actual byte progress · case 02

Range stream idle deadlines advance only on actual byte progress.

HTTP ranges◈ Members↗
FA-26623

Range stream idle deadlines advance only on actual byte progress · case 03

Range stream idle deadlines advance only on actual byte progress.

HTTP ranges◈ Members↗
FA-26624

Range stream idle deadlines advance only on actual byte progress · case 04

Range stream idle deadlines advance only on actual byte progress.

HTTP ranges◈ Members↗
FA-26625

Range stream idle deadlines advance only on actual byte progress · case 05

Range stream idle deadlines advance only on actual byte progress.

HTTP ranges◈ Members↗
FA-26626

Concurrent readers use positional I/O instead of a shared mutable seek cursor · case 01

Concurrent readers use positional I/O instead of a shared mutable seek cursor.

HTTP ranges● Open access↗
FA-26627

Concurrent readers use positional I/O instead of a shared mutable seek cursor · case 02

Concurrent readers use positional I/O instead of a shared mutable seek cursor.

HTTP ranges◈ Members↗
FA-26628

Concurrent readers use positional I/O instead of a shared mutable seek cursor · case 03

Concurrent readers use positional I/O instead of a shared mutable seek cursor.

HTTP ranges◈ Members↗
FA-26629

Concurrent readers use positional I/O instead of a shared mutable seek cursor · case 04

Concurrent readers use positional I/O instead of a shared mutable seek cursor.

HTTP ranges◈ Members↗
FA-26630

Concurrent readers use positional I/O instead of a shared mutable seek cursor · case 05

Concurrent readers use positional I/O instead of a shared mutable seek cursor.

HTTP ranges◈ Members↗
FA-26631

Multipart source handles remain open until every part finishes · case 01

Multipart source handles remain open until every part finishes.

HTTP ranges● Open access↗
FA-26632

Multipart source handles remain open until every part finishes · case 02

Multipart source handles remain open until every part finishes.

HTTP ranges◈ Members↗
FA-26633

Multipart source handles remain open until every part finishes · case 03

Multipart source handles remain open until every part finishes.

HTTP ranges◈ Members↗
FA-26634

Multipart source handles remain open until every part finishes · case 04

Multipart source handles remain open until every part finishes.

HTTP ranges◈ Members↗
FA-26635

Multipart source handles remain open until every part finishes · case 05

Multipart source handles remain open until every part finishes.

HTTP ranges◈ Members↗
FA-26636

A transport reset cannot leave queued range bytes available for transmission · case 01

A transport reset cannot leave queued range bytes available for transmission.

HTTP ranges● Open access↗
FA-26637

A transport reset cannot leave queued range bytes available for transmission · case 02

A transport reset cannot leave queued range bytes available for transmission.

HTTP ranges◈ Members↗
FA-26638

A transport reset cannot leave queued range bytes available for transmission · case 03

A transport reset cannot leave queued range bytes available for transmission.

HTTP ranges◈ Members↗
FA-26639

A transport reset cannot leave queued range bytes available for transmission · case 04

A transport reset cannot leave queued range bytes available for transmission.

HTTP ranges◈ Members↗
FA-26640

A transport reset cannot leave queued range bytes available for transmission · case 05

A transport reset cannot leave queued range bytes available for transmission.

HTTP ranges◈ Members↗
FA-26641

Repeated Range fields combine their member lists under one unit · case 01

Repeated Range fields combine their member lists under one unit.

HTTP ranges● Open access↗
FA-26642

Repeated Range fields combine their member lists under one unit · case 02

Repeated Range fields combine their member lists under one unit.

HTTP ranges◈ Members↗
FA-26643

Repeated Range fields combine their member lists under one unit · case 03

Repeated Range fields combine their member lists under one unit.

HTTP ranges◈ Members↗
FA-26644

Repeated Range fields combine their member lists under one unit · case 04

Repeated Range fields combine their member lists under one unit.

HTTP ranges◈ Members↗
FA-26645

Repeated Range fields combine their member lists under one unit · case 05

Repeated Range fields combine their member lists under one unit.

HTTP ranges◈ Members↗
FA-26646

An empty list member invalidates this strict Range parser · case 01

An empty list member invalidates this strict Range parser.

HTTP ranges● Open access↗
FA-26647

An empty list member invalidates this strict Range parser · case 02

An empty list member invalidates this strict Range parser.

HTTP ranges◈ Members↗
FA-26648

An empty list member invalidates this strict Range parser · case 03

An empty list member invalidates this strict Range parser.

HTTP ranges◈ Members↗
FA-26649

An empty list member invalidates this strict Range parser · case 04

An empty list member invalidates this strict Range parser.

HTTP ranges◈ Members↗
FA-26650

An empty list member invalidates this strict Range parser · case 05

An empty list member invalidates this strict Range parser.

HTTP ranges◈ Members↗
FA-26651

Byte-range numbers reject non-ASCII decimal lookalikes · case 01

Byte-range numbers reject non-ASCII decimal lookalikes.

HTTP ranges● Open access↗
FA-26652

Byte-range numbers reject non-ASCII decimal lookalikes · case 02

Byte-range numbers reject non-ASCII decimal lookalikes.

HTTP ranges◈ Members↗
FA-26653

Byte-range numbers reject non-ASCII decimal lookalikes · case 03

Byte-range numbers reject non-ASCII decimal lookalikes.

HTTP ranges◈ Members↗
FA-26654

Byte-range numbers reject non-ASCII decimal lookalikes · case 04

Byte-range numbers reject non-ASCII decimal lookalikes.

HTTP ranges◈ Members↗
FA-26655

Byte-range numbers reject non-ASCII decimal lookalikes · case 05

Byte-range numbers reject non-ASCII decimal lookalikes.

HTTP ranges◈ Members↗
FA-26656

A range member has exactly one separator dash · case 01

A range member has exactly one separator dash.

HTTP ranges● Open access↗
FA-26657

A range member has exactly one separator dash · case 02

A range member has exactly one separator dash.

HTTP ranges◈ Members↗
FA-26658

A range member has exactly one separator dash · case 03

A range member has exactly one separator dash.

HTTP ranges◈ Members↗
FA-26659

A range member has exactly one separator dash · case 04

A range member has exactly one separator dash.

HTTP ranges◈ Members↗
FA-26660

A range member has exactly one separator dash · case 05

A range member has exactly one separator dash.

HTTP ranges◈ Members↗
FA-26661

Unsupported range units fall back to the full representation · case 01

Unsupported range units fall back to the full representation.

HTTP ranges● Open access↗
FA-26662

Unsupported range units fall back to the full representation · case 02

Unsupported range units fall back to the full representation.

HTTP ranges◈ Members↗
FA-26663

Unsupported range units fall back to the full representation · case 03

Unsupported range units fall back to the full representation.

HTTP ranges◈ Members↗
FA-26664

Unsupported range units fall back to the full representation · case 04

Unsupported range units fall back to the full representation.

HTTP ranges◈ Members↗
FA-26665

Unsupported range units fall back to the full representation · case 05

Unsupported range units fall back to the full representation.

HTTP ranges◈ Members↗
FA-26666

Only outer optional whitespace is accepted around range unit tokens · case 01

Only outer optional whitespace is accepted around range unit tokens.

HTTP ranges● Open access↗
FA-26667

Only outer optional whitespace is accepted around range unit tokens · case 02

Only outer optional whitespace is accepted around range unit tokens.

HTTP ranges◈ Members↗
FA-26668

Only outer optional whitespace is accepted around range unit tokens · case 03

Only outer optional whitespace is accepted around range unit tokens.

HTTP ranges◈ Members↗
FA-26669

Only outer optional whitespace is accepted around range unit tokens · case 04

Only outer optional whitespace is accepted around range unit tokens.

HTTP ranges◈ Members↗
FA-26670

Only outer optional whitespace is accepted around range unit tokens · case 05

Only outer optional whitespace is accepted around range unit tokens.

HTTP ranges◈ Members↗
FA-26671

Request member limits apply before deduplication · case 01

Request member limits apply before deduplication.

HTTP ranges● Open access↗
FA-26672

Request member limits apply before deduplication · case 02

Request member limits apply before deduplication.

HTTP ranges◈ Members↗
FA-26673

Request member limits apply before deduplication · case 03

Request member limits apply before deduplication.

HTTP ranges◈ Members↗
FA-26674

Request member limits apply before deduplication · case 04

Request member limits apply before deduplication.

HTTP ranges◈ Members↗
FA-26675

Request member limits apply before deduplication · case 05

Request member limits apply before deduplication.

HTTP ranges◈ Members↗
FA-26676

Numeric token budgets count leading zeroes before integer conversion · case 01

Numeric token budgets count leading zeroes before integer conversion.

HTTP ranges● Open access↗
FA-26677

Numeric token budgets count leading zeroes before integer conversion · case 02

Numeric token budgets count leading zeroes before integer conversion.

HTTP ranges◈ Members↗
FA-26678

Numeric token budgets count leading zeroes before integer conversion · case 03

Numeric token budgets count leading zeroes before integer conversion.

HTTP ranges◈ Members↗
FA-26679

Numeric token budgets count leading zeroes before integer conversion · case 04

Numeric token budgets count leading zeroes before integer conversion.

HTTP ranges◈ Members↗
FA-26680

Numeric token budgets count leading zeroes before integer conversion · case 05

Numeric token budgets count leading zeroes before integer conversion.

HTTP ranges◈ Members↗
FA-26681

A malformed member invalidates the whole stipulated strict range list · case 01

A malformed member invalidates the whole stipulated strict range list.

HTTP ranges● Open access↗
FA-26682

A malformed member invalidates the whole stipulated strict range list · case 02

A malformed member invalidates the whole stipulated strict range list.

HTTP ranges◈ Members↗
FA-26683

A malformed member invalidates the whole stipulated strict range list · case 03

A malformed member invalidates the whole stipulated strict range list.

HTTP ranges◈ Members↗
FA-26684

A malformed member invalidates the whole stipulated strict range list · case 04

A malformed member invalidates the whole stipulated strict range list.

HTTP ranges◈ Members↗
FA-26685

A malformed member invalidates the whole stipulated strict range list · case 05

A malformed member invalidates the whole stipulated strict range list.

HTTP ranges◈ Members↗
FA-26686

Range header budgets include commas and unit prefix bytes · case 01

Range header budgets include commas and unit prefix bytes.

HTTP ranges● Open access↗
FA-26687

Range header budgets include commas and unit prefix bytes · case 02

Range header budgets include commas and unit prefix bytes.

HTTP ranges◈ Members↗
FA-26688

Range header budgets include commas and unit prefix bytes · case 03

Range header budgets include commas and unit prefix bytes.

HTTP ranges◈ Members↗
FA-26689

Range header budgets include commas and unit prefix bytes · case 04

Range header budgets include commas and unit prefix bytes.

HTTP ranges◈ Members↗
FA-26690

Range header budgets include commas and unit prefix bytes · case 05

Range header budgets include commas and unit prefix bytes.

HTTP ranges◈ Members↗
FA-26691

Unknown complete lengths serialize as an asterisk · case 01

Unknown complete lengths serialize as an asterisk.

HTTP ranges● Open access↗
FA-26692

Unknown complete lengths serialize as an asterisk · case 02

Unknown complete lengths serialize as an asterisk.

HTTP ranges◈ Members↗
FA-26693

Unknown complete lengths serialize as an asterisk · case 03

Unknown complete lengths serialize as an asterisk.

HTTP ranges◈ Members↗
FA-26694

Unknown complete lengths serialize as an asterisk · case 04

Unknown complete lengths serialize as an asterisk.

HTTP ranges◈ Members↗
FA-26695

Unknown complete lengths serialize as an asterisk · case 05

Unknown complete lengths serialize as an asterisk.

HTTP ranges◈ Members↗
FA-26696

Unsatisfied range metadata reports the complete length without invented endpoints · case 01

Unsatisfied range metadata reports the complete length without invented endpoints.

HTTP ranges● Open access↗
FA-26697

Unsatisfied range metadata reports the complete length without invented endpoints · case 02

Unsatisfied range metadata reports the complete length without invented endpoints.

HTTP ranges◈ Members↗
FA-26698

Unsatisfied range metadata reports the complete length without invented endpoints · case 03

Unsatisfied range metadata reports the complete length without invented endpoints.

HTTP ranges◈ Members↗
FA-26699

Unsatisfied range metadata reports the complete length without invented endpoints · case 04

Unsatisfied range metadata reports the complete length without invented endpoints.

HTTP ranges◈ Members↗
FA-26700

Unsatisfied range metadata reports the complete length without invented endpoints · case 05

Unsatisfied range metadata reports the complete length without invented endpoints.

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 ↗