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

A remote archive reader locates the central directory from a suffix range response: only a directory starting inside the tail is served locally · case 01

A remote archive reader locates the central directory from a suffix range response: only a directory starting inside the tail is served locally.

HTTP ranges● Open access↗
FA-27702

A remote archive reader locates the central directory from a suffix range response: only a directory starting inside the tail is served locally · case 02

A remote archive reader locates the central directory from a suffix range response: only a directory starting inside the tail is served locally.

HTTP ranges◈ Members↗
FA-27703

A remote archive reader locates the central directory from a suffix range response: only a directory starting inside the tail is served locally · case 03

A remote archive reader locates the central directory from a suffix range response: only a directory starting inside the tail is served locally.

HTTP ranges◈ Members↗
FA-27704

A remote archive reader locates the central directory from a suffix range response: only a directory starting inside the tail is served locally · case 04

A remote archive reader locates the central directory from a suffix range response: only a directory starting inside the tail is served locally.

HTTP ranges◈ Members↗
FA-27705

A remote archive reader locates the central directory from a suffix range response: only a directory starting inside the tail is served locally · case 05

A remote archive reader locates the central directory from a suffix range response: only a directory starting inside the tail is served locally.

HTTP ranges◈ Members↗
FA-27706

A remote archive reader locates the central directory from a suffix range response: the follow-up range stops before bytes already present in the tail · case 01

A remote archive reader locates the central directory from a suffix range response: the follow-up range stops before bytes already present in the tail.

HTTP ranges● Open access↗
FA-27707

A remote archive reader locates the central directory from a suffix range response: the follow-up range stops before bytes already present in the tail · case 02

A remote archive reader locates the central directory from a suffix range response: the follow-up range stops before bytes already present in the tail.

HTTP ranges◈ Members↗
FA-27708

A remote archive reader locates the central directory from a suffix range response: the follow-up range stops before bytes already present in the tail · case 03

A remote archive reader locates the central directory from a suffix range response: the follow-up range stops before bytes already present in the tail.

HTTP ranges◈ Members↗
FA-27709

A remote archive reader locates the central directory from a suffix range response: the follow-up range stops before bytes already present in the tail · case 04

A remote archive reader locates the central directory from a suffix range response: the follow-up range stops before bytes already present in the tail.

HTTP ranges◈ Members↗
FA-27710

A remote archive reader locates the central directory from a suffix range response: the follow-up range stops before bytes already present in the tail · case 05

A remote archive reader locates the central directory from a suffix range response: the follow-up range stops before bytes already present in the tail.

HTTP ranges◈ Members↗
FA-27711

A remote archive reader locates the central directory from a suffix range response: local directory slices use the recorded offset rather than end-record adjacency · case 01

A remote archive reader locates the central directory from a suffix range response: local directory slices use the recorded offset rather than end-record adjacency.

HTTP ranges● Open access↗
FA-27712

A remote archive reader locates the central directory from a suffix range response: local directory slices use the recorded offset rather than end-record adjacency · case 02

A remote archive reader locates the central directory from a suffix range response: local directory slices use the recorded offset rather than end-record adjacency.

HTTP ranges◈ Members↗
FA-27713

A remote archive reader locates the central directory from a suffix range response: local directory slices use the recorded offset rather than end-record adjacency · case 03

A remote archive reader locates the central directory from a suffix range response: local directory slices use the recorded offset rather than end-record adjacency.

HTTP ranges◈ Members↗
FA-27714

A remote archive reader locates the central directory from a suffix range response: local directory slices use the recorded offset rather than end-record adjacency · case 04

A remote archive reader locates the central directory from a suffix range response: local directory slices use the recorded offset rather than end-record adjacency.

HTTP ranges◈ Members↗
FA-27715

A remote archive reader locates the central directory from a suffix range response: local directory slices use the recorded offset rather than end-record adjacency · case 05

A remote archive reader locates the central directory from a suffix range response: local directory slices use the recorded offset rather than end-record adjacency.

HTTP ranges◈ Members↗
FA-27716

A remote archive reader locates the central directory from a suffix range response: an exhausted backward scan cannot fall through to an unchecked first tail byte · case 01

A remote archive reader locates the central directory from a suffix range response: an exhausted backward scan cannot fall through to an unchecked first tail byte.

HTTP ranges● Open access↗
FA-27717

A remote archive reader locates the central directory from a suffix range response: an exhausted backward scan cannot fall through to an unchecked first tail byte · case 02

A remote archive reader locates the central directory from a suffix range response: an exhausted backward scan cannot fall through to an unchecked first tail byte.

HTTP ranges◈ Members↗
FA-27718

A remote archive reader locates the central directory from a suffix range response: an exhausted backward scan cannot fall through to an unchecked first tail byte · case 03

A remote archive reader locates the central directory from a suffix range response: an exhausted backward scan cannot fall through to an unchecked first tail byte.

HTTP ranges◈ Members↗
FA-27719

A remote archive reader locates the central directory from a suffix range response: an exhausted backward scan cannot fall through to an unchecked first tail byte · case 04

A remote archive reader locates the central directory from a suffix range response: an exhausted backward scan cannot fall through to an unchecked first tail byte.

HTTP ranges◈ Members↗
FA-27720

A remote archive reader locates the central directory from a suffix range response: an exhausted backward scan cannot fall through to an unchecked first tail byte · case 05

A remote archive reader locates the central directory from a suffix range response: an exhausted backward scan cannot fall through to an unchecked first tail byte.

HTTP ranges◈ Members↗
FA-27721

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: matching content is found at any local block position · case 01

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: matching content is found at any local block position.

HTTP ranges● Open access↗
FA-27722

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: matching content is found at any local block position · case 02

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: matching content is found at any local block position.

HTTP ranges◈ Members↗
FA-27723

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: matching content is found at any local block position · case 03

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: matching content is found at any local block position.

HTTP ranges◈ Members↗
FA-27724

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: matching content is found at any local block position · case 04

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: matching content is found at any local block position.

HTTP ranges◈ Members↗
FA-27725

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: matching content is found at any local block position · case 05

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: matching content is found at any local block position.

HTTP ranges◈ Members↗
FA-27726

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short final remote block is fetched instead of matched against a full local block · case 01

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short final remote block is fetched instead of matched against a full local block.

HTTP ranges● Open access↗
FA-27727

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short final remote block is fetched instead of matched against a full local block · case 02

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short final remote block is fetched instead of matched against a full local block.

HTTP ranges◈ Members↗
FA-27728

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short final remote block is fetched instead of matched against a full local block · case 03

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short final remote block is fetched instead of matched against a full local block.

HTTP ranges◈ Members↗
FA-27729

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short final remote block is fetched instead of matched against a full local block · case 04

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short final remote block is fetched instead of matched against a full local block.

HTTP ranges◈ Members↗
FA-27730

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short final remote block is fetched instead of matched against a full local block · case 05

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short final remote block is fetched instead of matched against a full local block.

HTTP ranges◈ Members↗
FA-27731

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final remote block length is the remaining representation bytes · case 01

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final remote block length is the remaining representation bytes.

HTTP ranges● Open access↗
FA-27732

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final remote block length is the remaining representation bytes · case 02

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final remote block length is the remaining representation bytes.

HTTP ranges◈ Members↗
FA-27733

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final remote block length is the remaining representation bytes · case 03

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final remote block length is the remaining representation bytes.

HTTP ranges◈ Members↗
FA-27734

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final remote block length is the remaining representation bytes · case 04

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final remote block length is the remaining representation bytes.

HTTP ranges◈ Members↗
FA-27735

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final remote block length is the remaining representation bytes · case 05

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final remote block length is the remaining representation bytes.

HTTP ranges◈ Members↗
FA-27736

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: copy instructions address the local block by byte offset · case 01

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: copy instructions address the local block by byte offset.

HTTP ranges● Open access↗
FA-27737

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: copy instructions address the local block by byte offset · case 02

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: copy instructions address the local block by byte offset.

HTTP ranges◈ Members↗
FA-27738

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: copy instructions address the local block by byte offset · case 03

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: copy instructions address the local block by byte offset.

HTTP ranges◈ Members↗
FA-27739

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: copy instructions address the local block by byte offset · case 04

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: copy instructions address the local block by byte offset.

HTTP ranges◈ Members↗
FA-27740

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: copy instructions address the local block by byte offset · case 05

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: copy instructions address the local block by byte offset.

HTTP ranges◈ Members↗
FA-27741

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: only byte-adjacent missing blocks extend the current fetch run · case 01

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: only byte-adjacent missing blocks extend the current fetch run.

HTTP ranges● Open access↗
FA-27742

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: only byte-adjacent missing blocks extend the current fetch run · case 02

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: only byte-adjacent missing blocks extend the current fetch run.

HTTP ranges◈ Members↗
FA-27743

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: only byte-adjacent missing blocks extend the current fetch run · case 03

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: only byte-adjacent missing blocks extend the current fetch run.

HTTP ranges◈ Members↗
FA-27744

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: only byte-adjacent missing blocks extend the current fetch run · case 04

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: only byte-adjacent missing blocks extend the current fetch run.

HTTP ranges◈ Members↗
FA-27745

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: only byte-adjacent missing blocks extend the current fetch run · case 05

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: only byte-adjacent missing blocks extend the current fetch run.

HTTP ranges◈ Members↗
FA-27746

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: each request batch takes the next R runs from its own start · case 01

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: each request batch takes the next R runs from its own start.

HTTP ranges● Open access↗
FA-27747

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: each request batch takes the next R runs from its own start · case 02

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: each request batch takes the next R runs from its own start.

HTTP ranges◈ Members↗
FA-27748

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: each request batch takes the next R runs from its own start · case 03

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: each request batch takes the next R runs from its own start.

HTTP ranges◈ Members↗
FA-27749

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: each request batch takes the next R runs from its own start · case 04

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: each request batch takes the next R runs from its own start.

HTTP ranges◈ Members↗
FA-27750

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: each request batch takes the next R runs from its own start · case 05

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: each request batch takes the next R runs from its own start.

HTTP ranges◈ Members↗
FA-27751

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final partial batch of runs is still requested · case 01

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final partial batch of runs is still requested.

HTTP ranges● Open access↗
FA-27752

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final partial batch of runs is still requested · case 02

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final partial batch of runs is still requested.

HTTP ranges◈ Members↗
FA-27753

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final partial batch of runs is still requested · case 03

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final partial batch of runs is still requested.

HTTP ranges◈ Members↗
FA-27754

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final partial batch of runs is still requested · case 04

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final partial batch of runs is still requested.

HTTP ranges◈ Members↗
FA-27755

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final partial batch of runs is still requested · case 05

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the final partial batch of runs is still requested.

HTTP ranges◈ Members↗
FA-27756

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the digest manifest must describe exactly the remote block count · case 01

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the digest manifest must describe exactly the remote block count.

HTTP ranges● Open access↗
FA-27757

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the digest manifest must describe exactly the remote block count · case 02

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the digest manifest must describe exactly the remote block count.

HTTP ranges◈ Members↗
FA-27758

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the digest manifest must describe exactly the remote block count · case 03

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the digest manifest must describe exactly the remote block count.

HTTP ranges◈ Members↗
FA-27759

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the digest manifest must describe exactly the remote block count · case 04

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the digest manifest must describe exactly the remote block count.

HTTP ranges◈ Members↗
FA-27760

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the digest manifest must describe exactly the remote block count · case 05

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: the digest manifest must describe exactly the remote block count.

HTTP ranges◈ Members↗
FA-27761

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short local tail block is not a reusable full block · case 01

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short local tail block is not a reusable full block.

HTTP ranges● Open access↗
FA-27762

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short local tail block is not a reusable full block · case 02

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short local tail block is not a reusable full block.

HTTP ranges◈ Members↗
FA-27763

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short local tail block is not a reusable full block · case 03

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short local tail block is not a reusable full block.

HTTP ranges◈ Members↗
FA-27764

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short local tail block is not a reusable full block · case 04

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short local tail block is not a reusable full block.

HTTP ranges◈ Members↗
FA-27765

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short local tail block is not a reusable full block · case 05

A delta downloader reuses matching local blocks and fetches the rest with batched ranges: a short local tail block is not a reusable full block.

HTTP ranges◈ Members↗
FA-27766

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range starts at the byte after the previous sub-range · case 01

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range starts at the byte after the previous sub-range.

HTTP ranges● Open access↗
FA-27767

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range starts at the byte after the previous sub-range · case 02

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range starts at the byte after the previous sub-range.

HTTP ranges◈ Members↗
FA-27768

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range starts at the byte after the previous sub-range · case 03

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range starts at the byte after the previous sub-range.

HTTP ranges◈ Members↗
FA-27769

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range starts at the byte after the previous sub-range · case 04

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range starts at the byte after the previous sub-range.

HTTP ranges◈ Members↗
FA-27770

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range starts at the byte after the previous sub-range · case 05

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range starts at the byte after the previous sub-range.

HTTP ranges◈ Members↗
FA-27771

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range cannot continue a different resource · case 01

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range cannot continue a different resource.

HTTP ranges● Open access↗
FA-27772

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range cannot continue a different resource · case 02

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range cannot continue a different resource.

HTTP ranges◈ Members↗
FA-27773

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range cannot continue a different resource · case 03

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range cannot continue a different resource.

HTTP ranges◈ Members↗
FA-27774

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range cannot continue a different resource · case 04

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range cannot continue a different resource.

HTTP ranges◈ Members↗
FA-27775

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range cannot continue a different resource · case 05

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range cannot continue a different resource.

HTTP ranges◈ Members↗
FA-27776

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range without a preceding sub-range is invalid rather than starting at zero · case 01

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range without a preceding sub-range is invalid rather than starting at zero.

HTTP ranges● Open access↗
FA-27777

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range without a preceding sub-range is invalid rather than starting at zero · case 02

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range without a preceding sub-range is invalid rather than starting at zero.

HTTP ranges◈ Members↗
FA-27778

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range without a preceding sub-range is invalid rather than starting at zero · case 03

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range without a preceding sub-range is invalid rather than starting at zero.

HTTP ranges◈ Members↗
FA-27779

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range without a preceding sub-range is invalid rather than starting at zero · case 04

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range without a preceding sub-range is invalid rather than starting at zero.

HTTP ranges◈ Members↗
FA-27780

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range without a preceding sub-range is invalid rather than starting at zero · case 05

A segment playlist resolves byte-range tags into per-segment Range values: an offsetless sub-range without a preceding sub-range is invalid rather than starting at zero.

HTTP ranges◈ Members↗
FA-27781

A segment playlist resolves byte-range tags into per-segment Range values: a byte-range tag applies only to the next segment URI · case 01

A segment playlist resolves byte-range tags into per-segment Range values: a byte-range tag applies only to the next segment URI.

HTTP ranges● Open access↗
FA-27782

A segment playlist resolves byte-range tags into per-segment Range values: a byte-range tag applies only to the next segment URI · case 02

A segment playlist resolves byte-range tags into per-segment Range values: a byte-range tag applies only to the next segment URI.

HTTP ranges◈ Members↗
FA-27783

A segment playlist resolves byte-range tags into per-segment Range values: a byte-range tag applies only to the next segment URI · case 03

A segment playlist resolves byte-range tags into per-segment Range values: a byte-range tag applies only to the next segment URI.

HTTP ranges◈ Members↗
FA-27784

A segment playlist resolves byte-range tags into per-segment Range values: a byte-range tag applies only to the next segment URI · case 04

A segment playlist resolves byte-range tags into per-segment Range values: a byte-range tag applies only to the next segment URI.

HTTP ranges◈ Members↗
FA-27785

A segment playlist resolves byte-range tags into per-segment Range values: a byte-range tag applies only to the next segment URI · case 05

A segment playlist resolves byte-range tags into per-segment Range values: a byte-range tag applies only to the next segment URI.

HTTP ranges◈ Members↗
FA-27786

A segment playlist resolves byte-range tags into per-segment Range values: a whole-resource segment breaks the implicit offset chain · case 01

A segment playlist resolves byte-range tags into per-segment Range values: a whole-resource segment breaks the implicit offset chain.

HTTP ranges● Open access↗
FA-27787

A segment playlist resolves byte-range tags into per-segment Range values: a whole-resource segment breaks the implicit offset chain · case 02

A segment playlist resolves byte-range tags into per-segment Range values: a whole-resource segment breaks the implicit offset chain.

HTTP ranges◈ Members↗
FA-27788

A segment playlist resolves byte-range tags into per-segment Range values: a whole-resource segment breaks the implicit offset chain · case 03

A segment playlist resolves byte-range tags into per-segment Range values: a whole-resource segment breaks the implicit offset chain.

HTTP ranges◈ Members↗
FA-27789

A segment playlist resolves byte-range tags into per-segment Range values: a whole-resource segment breaks the implicit offset chain · case 04

A segment playlist resolves byte-range tags into per-segment Range values: a whole-resource segment breaks the implicit offset chain.

HTTP ranges◈ Members↗
FA-27790

A segment playlist resolves byte-range tags into per-segment Range values: a whole-resource segment breaks the implicit offset chain · case 05

A segment playlist resolves byte-range tags into per-segment Range values: a whole-resource segment breaks the implicit offset chain.

HTTP ranges◈ Members↗
FA-27791

A segment playlist resolves byte-range tags into per-segment Range values: a zero-byte sub-range cannot be expressed as an inclusive Range · case 01

A segment playlist resolves byte-range tags into per-segment Range values: a zero-byte sub-range cannot be expressed as an inclusive Range.

HTTP ranges● Open access↗
FA-27792

A segment playlist resolves byte-range tags into per-segment Range values: a zero-byte sub-range cannot be expressed as an inclusive Range · case 02

A segment playlist resolves byte-range tags into per-segment Range values: a zero-byte sub-range cannot be expressed as an inclusive Range.

HTTP ranges◈ Members↗
FA-27793

A segment playlist resolves byte-range tags into per-segment Range values: a zero-byte sub-range cannot be expressed as an inclusive Range · case 03

A segment playlist resolves byte-range tags into per-segment Range values: a zero-byte sub-range cannot be expressed as an inclusive Range.

HTTP ranges◈ Members↗
FA-27794

A segment playlist resolves byte-range tags into per-segment Range values: a zero-byte sub-range cannot be expressed as an inclusive Range · case 04

A segment playlist resolves byte-range tags into per-segment Range values: a zero-byte sub-range cannot be expressed as an inclusive Range.

HTTP ranges◈ Members↗
FA-27795

A segment playlist resolves byte-range tags into per-segment Range values: a zero-byte sub-range cannot be expressed as an inclusive Range · case 05

A segment playlist resolves byte-range tags into per-segment Range values: a zero-byte sub-range cannot be expressed as an inclusive Range.

HTTP ranges◈ Members↗
FA-27796

A segment playlist resolves byte-range tags into per-segment Range values: carriage returns from CRLF playlists are trimmed before parsing · case 01

A segment playlist resolves byte-range tags into per-segment Range values: carriage returns from CRLF playlists are trimmed before parsing.

HTTP ranges● Open access↗
FA-27797

A segment playlist resolves byte-range tags into per-segment Range values: carriage returns from CRLF playlists are trimmed before parsing · case 02

A segment playlist resolves byte-range tags into per-segment Range values: carriage returns from CRLF playlists are trimmed before parsing.

HTTP ranges◈ Members↗
FA-27798

A segment playlist resolves byte-range tags into per-segment Range values: carriage returns from CRLF playlists are trimmed before parsing · case 03

A segment playlist resolves byte-range tags into per-segment Range values: carriage returns from CRLF playlists are trimmed before parsing.

HTTP ranges◈ Members↗
FA-27799

A segment playlist resolves byte-range tags into per-segment Range values: carriage returns from CRLF playlists are trimmed before parsing · case 04

A segment playlist resolves byte-range tags into per-segment Range values: carriage returns from CRLF playlists are trimmed before parsing.

HTTP ranges◈ Members↗
FA-27800

A segment playlist resolves byte-range tags into per-segment Range values: carriage returns from CRLF playlists are trimmed before parsing · case 05

A segment playlist resolves byte-range tags into per-segment Range values: carriage returns from CRLF playlists are trimmed before parsing.

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 ↗