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

Http2 settings payload is multiple of six · case 01

Http2 settings payload is multiple of six.

Multiplexed protocols● Open access↗
FA-7502

Http2 settings payload is multiple of six · case 02

Http2 settings payload is multiple of six.

Multiplexed protocols◈ Members↗
FA-7503

Http2 settings payload is multiple of six · case 03

Http2 settings payload is multiple of six.

Multiplexed protocols◈ Members↗
FA-7504

Http2 settings payload is multiple of six · case 04

Http2 settings payload is multiple of six.

Multiplexed protocols◈ Members↗
FA-7505

Http2 settings payload is multiple of six · case 05

Http2 settings payload is multiple of six.

Multiplexed protocols◈ Members↗
FA-7506

Http2 ping requires zero stream and eight byte payload · case 01

Http2 ping requires zero stream and eight byte payload.

Multiplexed protocols● Open access↗
FA-7507

Http2 ping requires zero stream and eight byte payload · case 02

Http2 ping requires zero stream and eight byte payload.

Multiplexed protocols◈ Members↗
FA-7508

Http2 ping requires zero stream and eight byte payload · case 03

Http2 ping requires zero stream and eight byte payload.

Multiplexed protocols◈ Members↗
FA-7509

Http2 ping requires zero stream and eight byte payload · case 04

Http2 ping requires zero stream and eight byte payload.

Multiplexed protocols◈ Members↗
FA-7510

Http2 ping requires zero stream and eight byte payload · case 05

Http2 ping requires zero stream and eight byte payload.

Multiplexed protocols◈ Members↗
FA-7511

Http2 continuation must stay on the unfinished header stream · case 01

Http2 continuation must stay on the unfinished header stream.

Multiplexed protocols● Open access↗
FA-7512

Http2 continuation must stay on the unfinished header stream · case 02

Http2 continuation must stay on the unfinished header stream.

Multiplexed protocols◈ Members↗
FA-7513

Http2 continuation must stay on the unfinished header stream · case 03

Http2 continuation must stay on the unfinished header stream.

Multiplexed protocols◈ Members↗
FA-7514

Http2 continuation must stay on the unfinished header stream · case 04

Http2 continuation must stay on the unfinished header stream.

Multiplexed protocols◈ Members↗
FA-7515

Http2 continuation must stay on the unfinished header stream · case 05

Http2 continuation must stay on the unfinished header stream.

Multiplexed protocols◈ Members↗
FA-7516

Http2 pseudoheaders must precede regular fields · case 01

Http2 pseudoheaders must precede regular fields.

Multiplexed protocols● Open access↗
FA-7517

Http2 pseudoheaders must precede regular fields · case 02

Http2 pseudoheaders must precede regular fields.

Multiplexed protocols◈ Members↗
FA-7518

Http2 pseudoheaders must precede regular fields · case 03

Http2 pseudoheaders must precede regular fields.

Multiplexed protocols◈ Members↗
FA-7519

Http2 pseudoheaders must precede regular fields · case 04

Http2 pseudoheaders must precede regular fields.

Multiplexed protocols◈ Members↗
FA-7520

Http2 pseudoheaders must precede regular fields · case 05

Http2 pseudoheaders must precede regular fields.

Multiplexed protocols◈ Members↗
FA-7521

Http2 field names must be lowercase · case 01

Http2 field names must be lowercase.

Multiplexed protocols● Open access↗
FA-7522

Http2 field names must be lowercase · case 02

Http2 field names must be lowercase.

Multiplexed protocols◈ Members↗
FA-7523

Http2 field names must be lowercase · case 03

Http2 field names must be lowercase.

Multiplexed protocols◈ Members↗
FA-7524

Http2 field names must be lowercase · case 04

Http2 field names must be lowercase.

Multiplexed protocols◈ Members↗
FA-7525

Http2 field names must be lowercase · case 05

Http2 field names must be lowercase.

Multiplexed protocols◈ Members↗
FA-7526

Http2 goaway retry only streams above last processed id · case 01

Http2 goaway retry only streams above last processed id.

Multiplexed protocols● Open access↗
FA-7527

Http2 goaway retry only streams above last processed id · case 02

Http2 goaway retry only streams above last processed id.

Multiplexed protocols◈ Members↗
FA-7528

Http2 goaway retry only streams above last processed id · case 03

Http2 goaway retry only streams above last processed id.

Multiplexed protocols◈ Members↗
FA-7529

Http2 goaway retry only streams above last processed id · case 04

Http2 goaway retry only streams above last processed id.

Multiplexed protocols◈ Members↗
FA-7530

Http2 goaway retry only streams above last processed id · case 05

Http2 goaway retry only streams above last processed id.

Multiplexed protocols◈ Members↗
FA-7531

Http2 priority stream cannot depend on itself · case 01

Http2 priority stream cannot depend on itself.

Multiplexed protocols● Open access↗
FA-7532

Http2 priority stream cannot depend on itself · case 02

Http2 priority stream cannot depend on itself.

Multiplexed protocols◈ Members↗
FA-7533

Http2 priority stream cannot depend on itself · case 03

Http2 priority stream cannot depend on itself.

Multiplexed protocols◈ Members↗
FA-7534

Http2 priority stream cannot depend on itself · case 04

Http2 priority stream cannot depend on itself.

Multiplexed protocols◈ Members↗
FA-7535

Http2 priority stream cannot depend on itself · case 05

Http2 priority stream cannot depend on itself.

Multiplexed protocols◈ Members↗
FA-7536

Http2 reset releases only the target stream · case 01

Http2 reset releases only the target stream.

Multiplexed protocols● Open access↗
FA-7537

Http2 reset releases only the target stream · case 02

Http2 reset releases only the target stream.

Multiplexed protocols◈ Members↗
FA-7538

Http2 reset releases only the target stream · case 03

Http2 reset releases only the target stream.

Multiplexed protocols◈ Members↗
FA-7539

Http2 reset releases only the target stream · case 04

Http2 reset releases only the target stream.

Multiplexed protocols◈ Members↗
FA-7540

Http2 reset releases only the target stream · case 05

Http2 reset releases only the target stream.

Multiplexed protocols◈ Members↗
FA-7541

Quic stream initiator is lowest identifier bit · case 01

Quic stream initiator is lowest identifier bit.

Multiplexed protocols● Open access↗
FA-7542

Quic stream initiator is lowest identifier bit · case 02

Quic stream initiator is lowest identifier bit.

Multiplexed protocols◈ Members↗
FA-7543

Quic stream initiator is lowest identifier bit · case 03

Quic stream initiator is lowest identifier bit.

Multiplexed protocols◈ Members↗
FA-7544

Quic stream initiator is lowest identifier bit · case 04

Quic stream initiator is lowest identifier bit.

Multiplexed protocols◈ Members↗
FA-7545

Quic stream initiator is lowest identifier bit · case 05

Quic stream initiator is lowest identifier bit.

Multiplexed protocols◈ Members↗
FA-7546

Quic stream direction is second identifier bit · case 01

Quic stream direction is second identifier bit.

Multiplexed protocols● Open access↗
FA-7547

Quic stream direction is second identifier bit · case 02

Quic stream direction is second identifier bit.

Multiplexed protocols◈ Members↗
FA-7548

Quic stream direction is second identifier bit · case 03

Quic stream direction is second identifier bit.

Multiplexed protocols◈ Members↗
FA-7549

Quic stream direction is second identifier bit · case 04

Quic stream direction is second identifier bit.

Multiplexed protocols◈ Members↗
FA-7550

Quic stream direction is second identifier bit · case 05

Quic stream direction is second identifier bit.

Multiplexed protocols◈ Members↗
FA-7551

Quic stream count limit converts index to one based count · case 01

Quic stream count limit converts index to one based count.

Multiplexed protocols● Open access↗
FA-7552

Quic stream count limit converts index to one based count · case 02

Quic stream count limit converts index to one based count.

Multiplexed protocols◈ Members↗
FA-7553

Quic stream count limit converts index to one based count · case 03

Quic stream count limit converts index to one based count.

Multiplexed protocols◈ Members↗
FA-7554

Quic stream count limit converts index to one based count · case 04

Quic stream count limit converts index to one based count.

Multiplexed protocols◈ Members↗
FA-7555

Quic stream count limit converts index to one based count · case 05

Quic stream count limit converts index to one based count.

Multiplexed protocols◈ Members↗
FA-7556

Quic max data updates are monotonic · case 01

Quic max data updates are monotonic.

Multiplexed protocols● Open access↗
FA-7557

Quic max data updates are monotonic · case 02

Quic max data updates are monotonic.

Multiplexed protocols◈ Members↗
FA-7558

Quic max data updates are monotonic · case 03

Quic max data updates are monotonic.

Multiplexed protocols◈ Members↗
FA-7559

Quic max data updates are monotonic · case 04

Quic max data updates are monotonic.

Multiplexed protocols◈ Members↗
FA-7560

Quic max data updates are monotonic · case 05

Quic max data updates are monotonic.

Multiplexed protocols◈ Members↗
FA-7561

Quic final size cannot change after fin · case 01

Quic final size cannot change after fin.

Multiplexed protocols● Open access↗
FA-7562

Quic final size cannot change after fin · case 02

Quic final size cannot change after fin.

Multiplexed protocols◈ Members↗
FA-7563

Quic final size cannot change after fin · case 03

Quic final size cannot change after fin.

Multiplexed protocols◈ Members↗
FA-7564

Quic final size cannot change after fin · case 04

Quic final size cannot change after fin.

Multiplexed protocols◈ Members↗
FA-7565

Quic final size cannot change after fin · case 05

Quic final size cannot change after fin.

Multiplexed protocols◈ Members↗
FA-7566

Quic stream offset plus length cannot exceed final size · case 01

Quic stream offset plus length cannot exceed final size.

Multiplexed protocols● Open access↗
FA-7567

Quic stream offset plus length cannot exceed final size · case 02

Quic stream offset plus length cannot exceed final size.

Multiplexed protocols◈ Members↗
FA-7568

Quic stream offset plus length cannot exceed final size · case 03

Quic stream offset plus length cannot exceed final size.

Multiplexed protocols◈ Members↗
FA-7569

Quic stream offset plus length cannot exceed final size · case 04

Quic stream offset plus length cannot exceed final size.

Multiplexed protocols◈ Members↗
FA-7570

Quic stream offset plus length cannot exceed final size · case 05

Quic stream offset plus length cannot exceed final size.

Multiplexed protocols◈ Members↗
FA-7571

Quic amplification budget applies before address validation · case 01

Quic amplification budget applies before address validation.

Multiplexed protocols● Open access↗
FA-7572

Quic amplification budget applies before address validation · case 02

Quic amplification budget applies before address validation.

Multiplexed protocols◈ Members↗
FA-7573

Quic amplification budget applies before address validation · case 03

Quic amplification budget applies before address validation.

Multiplexed protocols◈ Members↗
FA-7574

Quic amplification budget applies before address validation · case 04

Quic amplification budget applies before address validation.

Multiplexed protocols◈ Members↗
FA-7575

Quic amplification budget applies before address validation · case 05

Quic amplification budget applies before address validation.

Multiplexed protocols◈ Members↗
FA-7576

Quic ack delay is subtracted only up to peer limit · case 01

Quic ack delay is subtracted only up to peer limit.

Multiplexed protocols● Open access↗
FA-7577

Quic ack delay is subtracted only up to peer limit · case 02

Quic ack delay is subtracted only up to peer limit.

Multiplexed protocols◈ Members↗
FA-7578

Quic ack delay is subtracted only up to peer limit · case 03

Quic ack delay is subtracted only up to peer limit.

Multiplexed protocols◈ Members↗
FA-7579

Quic ack delay is subtracted only up to peer limit · case 04

Quic ack delay is subtracted only up to peer limit.

Multiplexed protocols◈ Members↗
FA-7580

Quic ack delay is subtracted only up to peer limit · case 05

Quic ack delay is subtracted only up to peer limit.

Multiplexed protocols◈ Members↗
FA-7581

Websocket upgrade requires both upgrade and connection tokens · case 01

Websocket upgrade requires both upgrade and connection tokens.

WebSocket and browser transport policies● Open access↗
FA-7582

Websocket upgrade requires both upgrade and connection tokens · case 02

Websocket upgrade requires both upgrade and connection tokens.

WebSocket and browser transport policies◈ Members↗
FA-7583

Websocket upgrade requires both upgrade and connection tokens · case 03

Websocket upgrade requires both upgrade and connection tokens.

WebSocket and browser transport policies◈ Members↗
FA-7584

Websocket upgrade requires both upgrade and connection tokens · case 04

Websocket upgrade requires both upgrade and connection tokens.

WebSocket and browser transport policies◈ Members↗
FA-7585

Websocket upgrade requires both upgrade and connection tokens · case 05

Websocket upgrade requires both upgrade and connection tokens.

WebSocket and browser transport policies◈ Members↗
FA-7586

Websocket handshake response must be switching protocols · case 01

Websocket handshake response must be switching protocols.

WebSocket and browser transport policies● Open access↗
FA-7587

Websocket handshake response must be switching protocols · case 02

Websocket handshake response must be switching protocols.

WebSocket and browser transport policies◈ Members↗
FA-7588

Websocket handshake response must be switching protocols · case 03

Websocket handshake response must be switching protocols.

WebSocket and browser transport policies◈ Members↗
FA-7589

Websocket handshake response must be switching protocols · case 04

Websocket handshake response must be switching protocols.

WebSocket and browser transport policies◈ Members↗
FA-7590

Websocket handshake response must be switching protocols · case 05

Websocket handshake response must be switching protocols.

WebSocket and browser transport policies◈ Members↗
FA-7591

Websocket client frames require masking and server frames forbid it · case 01

Websocket client frames require masking and server frames forbid it.

WebSocket and browser transport policies● Open access↗
FA-7592

Websocket client frames require masking and server frames forbid it · case 02

Websocket client frames require masking and server frames forbid it.

WebSocket and browser transport policies◈ Members↗
FA-7593

Websocket client frames require masking and server frames forbid it · case 03

Websocket client frames require masking and server frames forbid it.

WebSocket and browser transport policies◈ Members↗
FA-7594

Websocket client frames require masking and server frames forbid it · case 04

Websocket client frames require masking and server frames forbid it.

WebSocket and browser transport policies◈ Members↗
FA-7595

Websocket client frames require masking and server frames forbid it · case 05

Websocket client frames require masking and server frames forbid it.

WebSocket and browser transport policies◈ Members↗
FA-7596

Websocket control frames must be final and at most 125 bytes · case 01

Websocket control frames must be final and at most 125 bytes.

WebSocket and browser transport policies● Open access↗
FA-7597

Websocket control frames must be final and at most 125 bytes · case 02

Websocket control frames must be final and at most 125 bytes.

WebSocket and browser transport policies◈ Members↗
FA-7598

Websocket control frames must be final and at most 125 bytes · case 03

Websocket control frames must be final and at most 125 bytes.

WebSocket and browser transport policies◈ Members↗
FA-7599

Websocket control frames must be final and at most 125 bytes · case 04

Websocket control frames must be final and at most 125 bytes.

WebSocket and browser transport policies◈ Members↗
FA-7600

Websocket control frames must be final and at most 125 bytes · case 05

Websocket control frames must be final and at most 125 bytes.

WebSocket and browser transport policies◈ 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 ↗