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

Challenge refresh without ordinary retry amplification: Ordinary config violates retry transition semantics · case 01

Ordinary config violates retry transition semantics

HTTP retries● Open access↗FA-30302

Challenge refresh without ordinary retry amplification: Ordinary config violates retry transition semantics · case 02

Ordinary config violates retry transition semantics

HTTP retries◈ Members↗FA-30303

Challenge refresh without ordinary retry amplification: Ordinary config violates retry transition semantics · case 03

Ordinary config violates retry transition semantics

HTTP retries◈ Members↗FA-30304

Challenge refresh without ordinary retry amplification: Ordinary config violates retry transition semantics · case 04

Ordinary config violates retry transition semantics

HTTP retries◈ Members↗FA-30305

Challenge refresh without ordinary retry amplification: Ordinary config violates retry transition semantics · case 05

Ordinary config violates retry transition semantics

HTTP retries◈ Members↗FA-30306

Challenge refresh without ordinary retry amplification: Refresh config violates retry transition semantics · case 01

Refresh config violates retry transition semantics

HTTP retries● Open access↗FA-30307

Challenge refresh without ordinary retry amplification: Refresh config violates retry transition semantics · case 02

Refresh config violates retry transition semantics

HTTP retries◈ Members↗FA-30308

Challenge refresh without ordinary retry amplification: Refresh config violates retry transition semantics · case 03

Refresh config violates retry transition semantics

HTTP retries◈ Members↗FA-30309

Challenge refresh without ordinary retry amplification: Refresh config violates retry transition semantics · case 04

Refresh config violates retry transition semantics

HTTP retries◈ Members↗FA-30310

Challenge refresh without ordinary retry amplification: Refresh config violates retry transition semantics · case 05

Refresh config violates retry transition semantics

HTTP retries◈ Members↗FA-30311

Challenge refresh without ordinary retry amplification: Begin generation violates retry transition semantics · case 01

Begin generation violates retry transition semantics

HTTP retries● Open access↗FA-30312

Challenge refresh without ordinary retry amplification: Begin generation violates retry transition semantics · case 02

Begin generation violates retry transition semantics

HTTP retries◈ Members↗FA-30313

Challenge refresh without ordinary retry amplification: Begin generation violates retry transition semantics · case 03

Begin generation violates retry transition semantics

HTTP retries◈ Members↗FA-30314

Challenge refresh without ordinary retry amplification: Begin generation violates retry transition semantics · case 04

Begin generation violates retry transition semantics

HTTP retries◈ Members↗FA-30315

Challenge refresh without ordinary retry amplification: Begin generation violates retry transition semantics · case 05

Begin generation violates retry transition semantics

HTTP retries◈ Members↗FA-30316

Challenge refresh without ordinary retry amplification: Network wait violates retry transition semantics · case 01

Network wait violates retry transition semantics

HTTP retries● Open access↗FA-30317

Challenge refresh without ordinary retry amplification: Network wait violates retry transition semantics · case 02

Network wait violates retry transition semantics

HTTP retries◈ Members↗FA-30318

Challenge refresh without ordinary retry amplification: Network wait violates retry transition semantics · case 03

Network wait violates retry transition semantics

HTTP retries◈ Members↗FA-30319

Challenge refresh without ordinary retry amplification: Network wait violates retry transition semantics · case 04

Network wait violates retry transition semantics

HTTP retries◈ Members↗FA-30320

Challenge refresh without ordinary retry amplification: Network wait violates retry transition semantics · case 05

Network wait violates retry transition semantics

HTTP retries◈ Members↗FA-30321

Challenge refresh without ordinary retry amplification: Network budget violates retry transition semantics · case 01

Network budget violates retry transition semantics

HTTP retries● Open access↗FA-30322

Challenge refresh without ordinary retry amplification: Network budget violates retry transition semantics · case 02

Network budget violates retry transition semantics

HTTP retries◈ Members↗FA-30323

Challenge refresh without ordinary retry amplification: Network budget violates retry transition semantics · case 03

Network budget violates retry transition semantics

HTTP retries◈ Members↗FA-30324

Challenge refresh without ordinary retry amplification: Network budget violates retry transition semantics · case 04

Network budget violates retry transition semantics

HTTP retries◈ Members↗FA-30325

Challenge refresh without ordinary retry amplification: Network budget violates retry transition semantics · case 05

Network budget violates retry transition semantics

HTTP retries◈ Members↗FA-30326

Challenge refresh without ordinary retry amplification: Network charge violates retry transition semantics · case 01

Network charge violates retry transition semantics

HTTP retries● Open access↗FA-30327

Challenge refresh without ordinary retry amplification: Network charge violates retry transition semantics · case 02

Network charge violates retry transition semantics

HTTP retries◈ Members↗FA-30328

Challenge refresh without ordinary retry amplification: Network charge violates retry transition semantics · case 03

Network charge violates retry transition semantics

HTTP retries◈ Members↗FA-30329

Challenge refresh without ordinary retry amplification: Network charge violates retry transition semantics · case 04

Network charge violates retry transition semantics

HTTP retries◈ Members↗FA-30330

Challenge refresh without ordinary retry amplification: Network charge violates retry transition semantics · case 05

Network charge violates retry transition semantics

HTTP retries◈ Members↗FA-30331

Challenge refresh without ordinary retry amplification: Coalesce violates retry transition semantics · case 01

Coalesce violates retry transition semantics

HTTP retries● Open access↗FA-30332

Challenge refresh without ordinary retry amplification: Coalesce violates retry transition semantics · case 02

Coalesce violates retry transition semantics

HTTP retries◈ Members↗FA-30333

Challenge refresh without ordinary retry amplification: Coalesce violates retry transition semantics · case 03

Coalesce violates retry transition semantics

HTTP retries◈ Members↗FA-30334

Challenge refresh without ordinary retry amplification: Coalesce violates retry transition semantics · case 04

Coalesce violates retry transition semantics

HTTP retries◈ Members↗FA-30335

Challenge refresh without ordinary retry amplification: Coalesce violates retry transition semantics · case 05

Coalesce violates retry transition semantics

HTTP retries◈ Members↗FA-30336

Challenge refresh without ordinary retry amplification: Refresh budget violates retry transition semantics · case 01

Refresh budget violates retry transition semantics

HTTP retries● Open access↗FA-30337

Challenge refresh without ordinary retry amplification: Refresh budget violates retry transition semantics · case 02

Refresh budget violates retry transition semantics

HTTP retries◈ Members↗FA-30338

Challenge refresh without ordinary retry amplification: Refresh budget violates retry transition semantics · case 03

Refresh budget violates retry transition semantics

HTTP retries◈ Members↗FA-30339

Challenge refresh without ordinary retry amplification: Refresh budget violates retry transition semantics · case 04

Refresh budget violates retry transition semantics

HTTP retries◈ Members↗FA-30340

Challenge refresh without ordinary retry amplification: Refresh budget violates retry transition semantics · case 05

Refresh budget violates retry transition semantics

HTTP retries◈ Members↗FA-30341

Challenge refresh without ordinary retry amplification: Refresh charge violates retry transition semantics · case 01

Refresh charge violates retry transition semantics

HTTP retries● Open access↗FA-30342

Challenge refresh without ordinary retry amplification: Refresh charge violates retry transition semantics · case 02

Refresh charge violates retry transition semantics

HTTP retries◈ Members↗FA-30343

Challenge refresh without ordinary retry amplification: Refresh charge violates retry transition semantics · case 03

Refresh charge violates retry transition semantics

HTTP retries◈ Members↗FA-30344

Challenge refresh without ordinary retry amplification: Refresh charge violates retry transition semantics · case 04

Refresh charge violates retry transition semantics

HTTP retries◈ Members↗FA-30345

Challenge refresh without ordinary retry amplification: Refresh charge violates retry transition semantics · case 05

Refresh charge violates retry transition semantics

HTTP retries◈ Members↗FA-30346

Challenge refresh without ordinary retry amplification: Refresh generation violates retry transition semantics · case 01

Refresh generation violates retry transition semantics

HTTP retries● Open access↗FA-30347

Challenge refresh without ordinary retry amplification: Refresh generation violates retry transition semantics · case 02

Refresh generation violates retry transition semantics

HTTP retries◈ Members↗FA-30348

Challenge refresh without ordinary retry amplification: Refresh generation violates retry transition semantics · case 03

Refresh generation violates retry transition semantics

HTTP retries◈ Members↗FA-30349

Challenge refresh without ordinary retry amplification: Refresh generation violates retry transition semantics · case 04

Refresh generation violates retry transition semantics

HTTP retries◈ Members↗FA-30350

Challenge refresh without ordinary retry amplification: Refresh generation violates retry transition semantics · case 05

Refresh generation violates retry transition semantics

HTTP retries◈ Members↗FA-30351

Challenge refresh without ordinary retry amplification: Refresh pending violates retry transition semantics · case 01

Refresh pending violates retry transition semantics

HTTP retries● Open access↗FA-30352

Challenge refresh without ordinary retry amplification: Refresh pending violates retry transition semantics · case 02

Refresh pending violates retry transition semantics

HTTP retries◈ Members↗FA-30353

Challenge refresh without ordinary retry amplification: Refresh pending violates retry transition semantics · case 03

Refresh pending violates retry transition semantics

HTTP retries◈ Members↗FA-30354

Challenge refresh without ordinary retry amplification: Refresh pending violates retry transition semantics · case 04

Refresh pending violates retry transition semantics

HTTP retries◈ Members↗FA-30355

Challenge refresh without ordinary retry amplification: Refresh pending violates retry transition semantics · case 05

Refresh pending violates retry transition semantics

HTTP retries◈ Members↗FA-30356

Challenge refresh without ordinary retry amplification: Refresh match violates retry transition semantics · case 01

Refresh match violates retry transition semantics

HTTP retries● Open access↗FA-30357

Challenge refresh without ordinary retry amplification: Refresh match violates retry transition semantics · case 02

Refresh match violates retry transition semantics

HTTP retries◈ Members↗FA-30358

Challenge refresh without ordinary retry amplification: Refresh match violates retry transition semantics · case 03

Refresh match violates retry transition semantics

HTTP retries◈ Members↗FA-30359

Challenge refresh without ordinary retry amplification: Refresh match violates retry transition semantics · case 04

Refresh match violates retry transition semantics

HTTP retries◈ Members↗FA-30360

Challenge refresh without ordinary retry amplification: Refresh match violates retry transition semantics · case 05

Refresh match violates retry transition semantics

HTTP retries◈ Members↗FA-30361

Challenge refresh without ordinary retry amplification: Refresh single delivery violates retry transition semantics · case 01

Refresh single delivery violates retry transition semantics

HTTP retries● Open access↗FA-30362

Challenge refresh without ordinary retry amplification: Refresh single delivery violates retry transition semantics · case 02

Refresh single delivery violates retry transition semantics

HTTP retries◈ Members↗FA-30363

Challenge refresh without ordinary retry amplification: Refresh single delivery violates retry transition semantics · case 03

Refresh single delivery violates retry transition semantics

HTTP retries◈ Members↗FA-30364

Challenge refresh without ordinary retry amplification: Refresh single delivery violates retry transition semantics · case 04

Refresh single delivery violates retry transition semantics

HTTP retries◈ Members↗FA-30365

Challenge refresh without ordinary retry amplification: Refresh single delivery violates retry transition semantics · case 05

Refresh single delivery violates retry transition semantics

HTTP retries◈ Members↗FA-30366

Challenge refresh without ordinary retry amplification: Refresh completion violates retry transition semantics · case 01

Refresh completion violates retry transition semantics

HTTP retries● Open access↗FA-30367

Challenge refresh without ordinary retry amplification: Refresh completion violates retry transition semantics · case 02

Refresh completion violates retry transition semantics

HTTP retries◈ Members↗FA-30368

Challenge refresh without ordinary retry amplification: Refresh completion violates retry transition semantics · case 03

Refresh completion violates retry transition semantics

HTTP retries◈ Members↗FA-30369

Challenge refresh without ordinary retry amplification: Refresh completion violates retry transition semantics · case 04

Refresh completion violates retry transition semantics

HTTP retries◈ Members↗FA-30370

Challenge refresh without ordinary retry amplification: Refresh completion violates retry transition semantics · case 05

Refresh completion violates retry transition semantics

HTTP retries◈ Members↗FA-30371

Challenge refresh without ordinary retry amplification: Success terminal violates retry transition semantics · case 01

Success terminal violates retry transition semantics

HTTP retries● Open access↗FA-30372

Challenge refresh without ordinary retry amplification: Success terminal violates retry transition semantics · case 02

Success terminal violates retry transition semantics

HTTP retries◈ Members↗FA-30373

Challenge refresh without ordinary retry amplification: Success terminal violates retry transition semantics · case 03

Success terminal violates retry transition semantics

HTTP retries◈ Members↗FA-30374

Challenge refresh without ordinary retry amplification: Success terminal violates retry transition semantics · case 04

Success terminal violates retry transition semantics

HTTP retries◈ Members↗FA-30375

Challenge refresh without ordinary retry amplification: Success terminal violates retry transition semantics · case 05

Success terminal violates retry transition semantics

HTTP retries◈ Members↗FA-30376

Logical request deadline across retry phases: Deadline anchor violates retry transition semantics · case 01

Deadline anchor violates retry transition semantics

HTTP retries● Open access↗FA-30377

Logical request deadline across retry phases: Deadline anchor violates retry transition semantics · case 02

Deadline anchor violates retry transition semantics

HTTP retries◈ Members↗FA-30378

Logical request deadline across retry phases: Deadline anchor violates retry transition semantics · case 03

Deadline anchor violates retry transition semantics

HTTP retries◈ Members↗FA-30379

Logical request deadline across retry phases: Deadline anchor violates retry transition semantics · case 04

Deadline anchor violates retry transition semantics

HTTP retries◈ Members↗FA-30380

Logical request deadline across retry phases: Deadline anchor violates retry transition semantics · case 05

Deadline anchor violates retry transition semantics

HTTP retries◈ Members↗FA-30381

Logical request deadline across retry phases: Clock monotonic violates retry transition semantics · case 01

Clock monotonic violates retry transition semantics

HTTP retries● Open access↗FA-30382

Logical request deadline across retry phases: Clock monotonic violates retry transition semantics · case 02

Clock monotonic violates retry transition semantics

HTTP retries◈ Members↗FA-30383

Logical request deadline across retry phases: Clock monotonic violates retry transition semantics · case 03

Clock monotonic violates retry transition semantics

HTTP retries◈ Members↗FA-30384

Logical request deadline across retry phases: Clock monotonic violates retry transition semantics · case 04

Clock monotonic violates retry transition semantics

HTTP retries◈ Members↗FA-30385

Logical request deadline across retry phases: Clock monotonic violates retry transition semantics · case 05

Clock monotonic violates retry transition semantics

HTTP retries◈ Members↗FA-30386

Logical request deadline across retry phases: New due reset violates retry transition semantics · case 01

New due reset violates retry transition semantics

HTTP retries● Open access↗FA-30387

Logical request deadline across retry phases: New due reset violates retry transition semantics · case 02

New due reset violates retry transition semantics

HTTP retries◈ Members↗FA-30388

Logical request deadline across retry phases: New due reset violates retry transition semantics · case 03

New due reset violates retry transition semantics

HTTP retries◈ Members↗FA-30389

Logical request deadline across retry phases: New due reset violates retry transition semantics · case 04

New due reset violates retry transition semantics

HTTP retries◈ Members↗FA-30390

Logical request deadline across retry phases: New due reset violates retry transition semantics · case 05

New due reset violates retry transition semantics

HTTP retries◈ Members↗FA-30391

Logical request deadline across retry phases: Cancel terminal violates retry transition semantics · case 01

Cancel terminal violates retry transition semantics

HTTP retries● Open access↗FA-30392

Logical request deadline across retry phases: Cancel terminal violates retry transition semantics · case 02

Cancel terminal violates retry transition semantics

HTTP retries◈ Members↗FA-30393

Logical request deadline across retry phases: Cancel terminal violates retry transition semantics · case 03

Cancel terminal violates retry transition semantics

HTTP retries◈ Members↗FA-30394

Logical request deadline across retry phases: Cancel terminal violates retry transition semantics · case 04

Cancel terminal violates retry transition semantics

HTTP retries◈ Members↗FA-30395

Logical request deadline across retry phases: Cancel terminal violates retry transition semantics · case 05

Cancel terminal violates retry transition semantics

HTTP retries◈ Members↗FA-30396

Logical request deadline across retry phases: Queue state violates retry transition semantics · case 01

Queue state violates retry transition semantics

HTTP retries● Open access↗FA-30397

Logical request deadline across retry phases: Queue state violates retry transition semantics · case 02

Queue state violates retry transition semantics

HTTP retries◈ Members↗FA-30398

Logical request deadline across retry phases: Queue state violates retry transition semantics · case 03

Queue state violates retry transition semantics

HTTP retries◈ Members↗FA-30399

Logical request deadline across retry phases: Queue state violates retry transition semantics · case 04

Queue state violates retry transition semantics

HTTP retries◈ Members↗FA-30400

Logical request deadline across retry phases: Queue state violates retry transition semantics · case 05

Queue state violates retry transition semantics

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