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

Cors non simple content type triggers preflight · case 01

Cors non simple content type triggers preflight.

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

Cors non simple content type triggers preflight · case 02

Cors non simple content type triggers preflight.

WebSocket and browser transport policies◈ Members↗
FA-7703

Cors non simple content type triggers preflight · case 03

Cors non simple content type triggers preflight.

WebSocket and browser transport policies◈ Members↗
FA-7704

Cors non simple content type triggers preflight · case 04

Cors non simple content type triggers preflight.

WebSocket and browser transport policies◈ Members↗
FA-7705

Cors non simple content type triggers preflight · case 05

Cors non simple content type triggers preflight.

WebSocket and browser transport policies◈ Members↗
FA-7706

Http11 default persistence is disabled by close token · case 01

Http11 default persistence is disabled by close token.

Connection lifecycle● Open access↗
FA-7707

Http11 default persistence is disabled by close token · case 02

Http11 default persistence is disabled by close token.

Connection lifecycle◈ Members↗
FA-7708

Http11 default persistence is disabled by close token · case 03

Http11 default persistence is disabled by close token.

Connection lifecycle◈ Members↗
FA-7709

Http11 default persistence is disabled by close token · case 04

Http11 default persistence is disabled by close token.

Connection lifecycle◈ Members↗
FA-7710

Http11 default persistence is disabled by close token · case 05

Http11 default persistence is disabled by close token.

Connection lifecycle◈ Members↗
FA-7711

Connection pool key includes scheme host and port · case 01

Connection pool key includes scheme host and port.

Connection lifecycle● Open access↗
FA-7712

Connection pool key includes scheme host and port · case 02

Connection pool key includes scheme host and port.

Connection lifecycle◈ Members↗
FA-7713

Connection pool key includes scheme host and port · case 03

Connection pool key includes scheme host and port.

Connection lifecycle◈ Members↗
FA-7714

Connection pool key includes scheme host and port · case 04

Connection pool key includes scheme host and port.

Connection lifecycle◈ Members↗
FA-7715

Connection pool key includes scheme host and port · case 05

Connection pool key includes scheme host and port.

Connection lifecycle◈ Members↗
FA-7716

Pool idle expiry measures time since last use · case 01

Pool idle expiry measures time since last use.

Connection lifecycle● Open access↗
FA-7717

Pool idle expiry measures time since last use · case 02

Pool idle expiry measures time since last use.

Connection lifecycle◈ Members↗
FA-7718

Pool idle expiry measures time since last use · case 03

Pool idle expiry measures time since last use.

Connection lifecycle◈ Members↗
FA-7719

Pool idle expiry measures time since last use · case 04

Pool idle expiry measures time since last use.

Connection lifecycle◈ Members↗
FA-7720

Pool idle expiry measures time since last use · case 05

Pool idle expiry measures time since last use.

Connection lifecycle◈ Members↗
FA-7721

Pool absolute lifetime is not reset by recent activity · case 01

Pool absolute lifetime is not reset by recent activity.

Connection lifecycle● Open access↗
FA-7722

Pool absolute lifetime is not reset by recent activity · case 02

Pool absolute lifetime is not reset by recent activity.

Connection lifecycle◈ Members↗
FA-7723

Pool absolute lifetime is not reset by recent activity · case 03

Pool absolute lifetime is not reset by recent activity.

Connection lifecycle◈ Members↗
FA-7724

Pool absolute lifetime is not reset by recent activity · case 04

Pool absolute lifetime is not reset by recent activity.

Connection lifecycle◈ Members↗
FA-7725

Pool absolute lifetime is not reset by recent activity · case 05

Pool absolute lifetime is not reset by recent activity.

Connection lifecycle◈ Members↗
FA-7726

Pool cap includes in progress connection attempts · case 01

Pool cap includes in progress connection attempts.

Connection lifecycle● Open access↗
FA-7727

Pool cap includes in progress connection attempts · case 02

Pool cap includes in progress connection attempts.

Connection lifecycle◈ Members↗
FA-7728

Pool cap includes in progress connection attempts · case 03

Pool cap includes in progress connection attempts.

Connection lifecycle◈ Members↗
FA-7729

Pool cap includes in progress connection attempts · case 04

Pool cap includes in progress connection attempts.

Connection lifecycle◈ Members↗
FA-7730

Pool cap includes in progress connection attempts · case 05

Pool cap includes in progress connection attempts.

Connection lifecycle◈ Members↗
FA-7731

Pool idle selection chooses most recently used healthy socket · case 01

Pool idle selection chooses most recently used healthy socket.

Connection lifecycle● Open access↗
FA-7732

Pool idle selection chooses most recently used healthy socket · case 02

Pool idle selection chooses most recently used healthy socket.

Connection lifecycle◈ Members↗
FA-7733

Pool idle selection chooses most recently used healthy socket · case 03

Pool idle selection chooses most recently used healthy socket.

Connection lifecycle◈ Members↗
FA-7734

Pool idle selection chooses most recently used healthy socket · case 04

Pool idle selection chooses most recently used healthy socket.

Connection lifecycle◈ Members↗
FA-7735

Pool idle selection chooses most recently used healthy socket · case 05

Pool idle selection chooses most recently used healthy socket.

Connection lifecycle◈ Members↗
FA-7736

Pool return requires complete message boundary · case 01

Pool return requires complete message boundary.

Connection lifecycle● Open access↗
FA-7737

Pool return requires complete message boundary · case 02

Pool return requires complete message boundary.

Connection lifecycle◈ Members↗
FA-7738

Pool return requires complete message boundary · case 03

Pool return requires complete message boundary.

Connection lifecycle◈ Members↗
FA-7739

Pool return requires complete message boundary · case 04

Pool return requires complete message boundary.

Connection lifecycle◈ Members↗
FA-7740

Pool return requires complete message boundary · case 05

Pool return requires complete message boundary.

Connection lifecycle◈ Members↗
FA-7741

Pool lease release removes one lease not every socket · case 01

Pool lease release removes one lease not every socket.

Connection lifecycle● Open access↗
FA-7742

Pool lease release removes one lease not every socket · case 02

Pool lease release removes one lease not every socket.

Connection lifecycle◈ Members↗
FA-7743

Pool lease release removes one lease not every socket · case 03

Pool lease release removes one lease not every socket.

Connection lifecycle◈ Members↗
FA-7744

Pool lease release removes one lease not every socket · case 04

Pool lease release removes one lease not every socket.

Connection lifecycle◈ Members↗
FA-7745

Pool lease release removes one lease not every socket · case 05

Pool lease release removes one lease not every socket.

Connection lifecycle◈ Members↗
FA-7746

Half close keeps receive direction open · case 01

Half close keeps receive direction open.

Connection lifecycle● Open access↗
FA-7747

Half close keeps receive direction open · case 02

Half close keeps receive direction open.

Connection lifecycle◈ Members↗
FA-7748

Half close keeps receive direction open · case 03

Half close keeps receive direction open.

Connection lifecycle◈ Members↗
FA-7749

Half close keeps receive direction open · case 04

Half close keeps receive direction open.

Connection lifecycle◈ Members↗
FA-7750

Half close keeps receive direction open · case 05

Half close keeps receive direction open.

Connection lifecycle◈ Members↗
FA-7751

Connect completion checks socket error not writability alone · case 01

Connect completion checks socket error not writability alone.

Connection lifecycle● Open access↗
FA-7752

Connect completion checks socket error not writability alone · case 02

Connect completion checks socket error not writability alone.

Connection lifecycle◈ Members↗
FA-7753

Connect completion checks socket error not writability alone · case 03

Connect completion checks socket error not writability alone.

Connection lifecycle◈ Members↗
FA-7754

Connect completion checks socket error not writability alone · case 04

Connect completion checks socket error not writability alone.

Connection lifecycle◈ Members↗
FA-7755

Connect completion checks socket error not writability alone · case 05

Connect completion checks socket error not writability alone.

Connection lifecycle◈ Members↗
FA-7756

Happy eyeballs second family starts after delay unless first failed · case 01

Happy eyeballs second family starts after delay unless first failed.

Connection lifecycle● Open access↗
FA-7757

Happy eyeballs second family starts after delay unless first failed · case 02

Happy eyeballs second family starts after delay unless first failed.

Connection lifecycle◈ Members↗
FA-7758

Happy eyeballs second family starts after delay unless first failed · case 03

Happy eyeballs second family starts after delay unless first failed.

Connection lifecycle◈ Members↗
FA-7759

Happy eyeballs second family starts after delay unless first failed · case 04

Happy eyeballs second family starts after delay unless first failed.

Connection lifecycle◈ Members↗
FA-7760

Happy eyeballs second family starts after delay unless first failed · case 05

Happy eyeballs second family starts after delay unless first failed.

Connection lifecycle◈ Members↗
FA-7761

Happy eyeballs winner cancels only other attempts · case 01

Happy eyeballs winner cancels only other attempts.

Connection lifecycle● Open access↗
FA-7762

Happy eyeballs winner cancels only other attempts · case 02

Happy eyeballs winner cancels only other attempts.

Connection lifecycle◈ Members↗
FA-7763

Happy eyeballs winner cancels only other attempts · case 03

Happy eyeballs winner cancels only other attempts.

Connection lifecycle◈ Members↗
FA-7764

Happy eyeballs winner cancels only other attempts · case 04

Happy eyeballs winner cancels only other attempts.

Connection lifecycle◈ Members↗
FA-7765

Happy eyeballs winner cancels only other attempts · case 05

Happy eyeballs winner cancels only other attempts.

Connection lifecycle◈ Members↗
FA-7766

Connection attempt timeout is separate from read timeout · case 01

Connection attempt timeout is separate from read timeout.

Connection lifecycle● Open access↗
FA-7767

Connection attempt timeout is separate from read timeout · case 02

Connection attempt timeout is separate from read timeout.

Connection lifecycle◈ Members↗
FA-7768

Connection attempt timeout is separate from read timeout · case 03

Connection attempt timeout is separate from read timeout.

Connection lifecycle◈ Members↗
FA-7769

Connection attempt timeout is separate from read timeout · case 04

Connection attempt timeout is separate from read timeout.

Connection lifecycle◈ Members↗
FA-7770

Connection attempt timeout is separate from read timeout · case 05

Connection attempt timeout is separate from read timeout.

Connection lifecycle◈ Members↗
FA-7771

Read progress resets idle deadline without extending total deadline · case 01

Read progress resets idle deadline without extending total deadline.

Connection lifecycle● Open access↗
FA-7772

Read progress resets idle deadline without extending total deadline · case 02

Read progress resets idle deadline without extending total deadline.

Connection lifecycle◈ Members↗
FA-7773

Read progress resets idle deadline without extending total deadline · case 03

Read progress resets idle deadline without extending total deadline.

Connection lifecycle◈ Members↗
FA-7774

Read progress resets idle deadline without extending total deadline · case 04

Read progress resets idle deadline without extending total deadline.

Connection lifecycle◈ Members↗
FA-7775

Read progress resets idle deadline without extending total deadline · case 05

Read progress resets idle deadline without extending total deadline.

Connection lifecycle◈ Members↗
FA-7776

Connection drain accepts existing streams but not new streams · case 01

Connection drain accepts existing streams but not new streams.

Connection lifecycle● Open access↗
FA-7777

Connection drain accepts existing streams but not new streams · case 02

Connection drain accepts existing streams but not new streams.

Connection lifecycle◈ Members↗
FA-7778

Connection drain accepts existing streams but not new streams · case 03

Connection drain accepts existing streams but not new streams.

Connection lifecycle◈ Members↗
FA-7779

Connection drain accepts existing streams but not new streams · case 04

Connection drain accepts existing streams but not new streams.

Connection lifecycle◈ Members↗
FA-7780

Connection drain accepts existing streams but not new streams · case 05

Connection drain accepts existing streams but not new streams.

Connection lifecycle◈ Members↗
FA-7781

Graceful drain completes when active stream count reaches zero · case 01

Graceful drain completes when active stream count reaches zero.

Connection lifecycle● Open access↗
FA-7782

Graceful drain completes when active stream count reaches zero · case 02

Graceful drain completes when active stream count reaches zero.

Connection lifecycle◈ Members↗
FA-7783

Graceful drain completes when active stream count reaches zero · case 03

Graceful drain completes when active stream count reaches zero.

Connection lifecycle◈ Members↗
FA-7784

Graceful drain completes when active stream count reaches zero · case 04

Graceful drain completes when active stream count reaches zero.

Connection lifecycle◈ Members↗
FA-7785

Graceful drain completes when active stream count reaches zero · case 05

Graceful drain completes when active stream count reaches zero.

Connection lifecycle◈ Members↗
FA-7786

Connection close notification is emitted once · case 01

Connection close notification is emitted once.

Connection lifecycle● Open access↗
FA-7787

Connection close notification is emitted once · case 02

Connection close notification is emitted once.

Connection lifecycle◈ Members↗
FA-7788

Connection close notification is emitted once · case 03

Connection close notification is emitted once.

Connection lifecycle◈ Members↗
FA-7789

Connection close notification is emitted once · case 04

Connection close notification is emitted once.

Connection lifecycle◈ Members↗
FA-7790

Connection close notification is emitted once · case 05

Connection close notification is emitted once.

Connection lifecycle◈ Members↗
FA-7791

Partial write advances only by successfully written count · case 01

Partial write advances only by successfully written count.

Connection lifecycle● Open access↗
FA-7792

Partial write advances only by successfully written count · case 02

Partial write advances only by successfully written count.

Connection lifecycle◈ Members↗
FA-7793

Partial write advances only by successfully written count · case 03

Partial write advances only by successfully written count.

Connection lifecycle◈ Members↗
FA-7794

Partial write advances only by successfully written count · case 04

Partial write advances only by successfully written count.

Connection lifecycle◈ Members↗
FA-7795

Partial write advances only by successfully written count · case 05

Partial write advances only by successfully written count.

Connection lifecycle◈ Members↗
FA-7796

Would block preserves entire unsent write buffer · case 01

Would block preserves entire unsent write buffer.

Connection lifecycle● Open access↗
FA-7797

Would block preserves entire unsent write buffer · case 02

Would block preserves entire unsent write buffer.

Connection lifecycle◈ Members↗
FA-7798

Would block preserves entire unsent write buffer · case 03

Would block preserves entire unsent write buffer.

Connection lifecycle◈ Members↗
FA-7799

Would block preserves entire unsent write buffer · case 04

Would block preserves entire unsent write buffer.

Connection lifecycle◈ Members↗
FA-7800

Would block preserves entire unsent write buffer · case 05

Would block preserves entire unsent write buffer.

Connection lifecycle◈ 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 ↗