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

Reopening a committed autocomplete: edit start selects only the old query prefix of the label · case 01

The selection completion transition produces an incorrect observable state.

Autocomplete interactions● Open access↗
FA-23302

Reopening a committed autocomplete: edit start selects only the old query prefix of the label · case 02

The selection completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23303

Reopening a committed autocomplete: edit start selects only the old query prefix of the label · case 03

The selection completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23304

Reopening a committed autocomplete: edit start selects only the old query prefix of the label · case 04

The selection completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23305

Reopening a committed autocomplete: edit start selects only the old query prefix of the label · case 05

The selection completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23306

Reopening a committed autocomplete: opening suggestions clears the committed value before an edit · case 01

The identity completion transition produces an incorrect observable state.

Autocomplete interactions● Open access↗
FA-23307

Reopening a committed autocomplete: opening suggestions clears the committed value before an edit · case 02

The identity completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23308

Reopening a committed autocomplete: opening suggestions clears the committed value before an edit · case 03

The identity completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23309

Reopening a committed autocomplete: opening suggestions clears the committed value before an edit · case 04

The identity completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23310

Reopening a committed autocomplete: opening suggestions clears the committed value before an edit · case 05

The identity completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23311

Reopening a committed autocomplete: editing the selected label retains an unrelated committed identifier · case 01

The diverged completion transition produces an incorrect observable state.

Autocomplete interactions● Open access↗
FA-23312

Reopening a committed autocomplete: editing the selected label retains an unrelated committed identifier · case 02

The diverged completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23313

Reopening a committed autocomplete: editing the selected label retains an unrelated committed identifier · case 03

The diverged completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23314

Reopening a committed autocomplete: editing the selected label retains an unrelated committed identifier · case 04

The diverged completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23315

Reopening a committed autocomplete: editing the selected label retains an unrelated committed identifier · case 05

The diverged completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23316

Reopening a committed autocomplete: editing compares to a previously selected label instead of current one · case 01

The baseline completion transition produces an incorrect observable state.

Autocomplete interactions● Open access↗
FA-23317

Reopening a committed autocomplete: editing compares to a previously selected label instead of current one · case 02

The baseline completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23318

Reopening a committed autocomplete: editing compares to a previously selected label instead of current one · case 03

The baseline completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23319

Reopening a committed autocomplete: editing compares to a previously selected label instead of current one · case 04

The baseline completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23320

Reopening a committed autocomplete: editing compares to a previously selected label instead of current one · case 05

The baseline completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23321

Reopening a committed autocomplete: programmatic accepted-label update triggers another lookup · case 01

The accepted-search completion transition produces an incorrect observable state.

Autocomplete interactions● Open access↗
FA-23322

Reopening a committed autocomplete: programmatic accepted-label update triggers another lookup · case 02

The accepted-search completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23323

Reopening a committed autocomplete: programmatic accepted-label update triggers another lookup · case 03

The accepted-search completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23324

Reopening a committed autocomplete: programmatic accepted-label update triggers another lookup · case 04

The accepted-search completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23325

Reopening a committed autocomplete: programmatic accepted-label update triggers another lookup · case 05

The accepted-search completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23326

Reopening a committed autocomplete: reopening chooses a former hover as the selection baseline · case 01

The selection-baseline completion transition produces an incorrect observable state.

Autocomplete interactions● Open access↗
FA-23327

Reopening a committed autocomplete: reopening chooses a former hover as the selection baseline · case 02

The selection-baseline completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23328

Reopening a committed autocomplete: reopening chooses a former hover as the selection baseline · case 03

The selection-baseline completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23329

Reopening a committed autocomplete: reopening chooses a former hover as the selection baseline · case 04

The selection-baseline completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23330

Reopening a committed autocomplete: reopening chooses a former hover as the selection baseline · case 05

The selection-baseline completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23331

Reopening a committed autocomplete: reopening marks a preserved unresolved draft as already accepted · case 01

The accepted-baseline completion transition produces an incorrect observable state.

Autocomplete interactions● Open access↗
FA-23332

Reopening a committed autocomplete: reopening marks a preserved unresolved draft as already accepted · case 02

The accepted-baseline completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23333

Reopening a committed autocomplete: reopening marks a preserved unresolved draft as already accepted · case 03

The accepted-baseline completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23334

Reopening a committed autocomplete: reopening marks a preserved unresolved draft as already accepted · case 04

The accepted-baseline completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23335

Reopening a committed autocomplete: reopening marks a preserved unresolved draft as already accepted · case 05

The accepted-baseline completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23336

Reopening a committed autocomplete: cancelling an edit reverts to an older selection label · case 01

The cancel-edit completion transition produces an incorrect observable state.

Autocomplete interactions● Open access↗
FA-23337

Reopening a committed autocomplete: cancelling an edit reverts to an older selection label · case 02

The cancel-edit completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23338

Reopening a committed autocomplete: cancelling an edit reverts to an older selection label · case 03

The cancel-edit completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23339

Reopening a committed autocomplete: cancelling an edit reverts to an older selection label · case 04

The cancel-edit completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23340

Reopening a committed autocomplete: cancelling an edit reverts to an older selection label · case 05

The cancel-edit completion transition produces an incorrect observable state.

Autocomplete interactions◈ Members↗
FA-23341

Hydration snapshot reconciliation: Dirty pre-hydration edits are overwritten · case 01

Dirty pre-hydration edits are overwritten.

Client state● Open access↗
FA-23342

Hydration snapshot reconciliation: Dirty pre-hydration edits are overwritten · case 02

Dirty pre-hydration edits are overwritten.

Client state◈ Members↗
FA-23343

Hydration snapshot reconciliation: Dirty pre-hydration edits are overwritten · case 03

Dirty pre-hydration edits are overwritten.

Client state◈ Members↗
FA-23344

Hydration snapshot reconciliation: Dirty pre-hydration edits are overwritten · case 04

Dirty pre-hydration edits are overwritten.

Client state◈ Members↗
FA-23345

Hydration snapshot reconciliation: Dirty pre-hydration edits are overwritten · case 05

Dirty pre-hydration edits are overwritten.

Client state◈ Members↗
FA-23346

Hydration snapshot reconciliation: Missing client properties erase server data · case 01

Missing client properties erase server data.

Client state● Open access↗
FA-23347

Hydration snapshot reconciliation: Missing client properties erase server data · case 02

Missing client properties erase server data.

Client state◈ Members↗
FA-23348

Hydration snapshot reconciliation: Missing client properties erase server data · case 03

Missing client properties erase server data.

Client state◈ Members↗
FA-23349

Hydration snapshot reconciliation: Missing client properties erase server data · case 04

Missing client properties erase server data.

Client state◈ Members↗
FA-23350

Hydration snapshot reconciliation: Missing client properties erase server data · case 05

Missing client properties erase server data.

Client state◈ Members↗
FA-23351

Hydration snapshot reconciliation: Older client snapshot blocks newer server revision · case 01

Older client snapshot blocks newer server revision.

Client state● Open access↗
FA-23352

Hydration snapshot reconciliation: Older client snapshot blocks newer server revision · case 02

Older client snapshot blocks newer server revision.

Client state◈ Members↗
FA-23353

Hydration snapshot reconciliation: Older client snapshot blocks newer server revision · case 03

Older client snapshot blocks newer server revision.

Client state◈ Members↗
FA-23354

Hydration snapshot reconciliation: Older client snapshot blocks newer server revision · case 04

Older client snapshot blocks newer server revision.

Client state◈ Members↗
FA-23355

Hydration snapshot reconciliation: Older client snapshot blocks newer server revision · case 05

Older client snapshot blocks newer server revision.

Client state◈ Members↗
FA-23356

Hydration snapshot reconciliation: Hydration completion is attributed to another root · case 01

Hydration completion is attributed to another root.

Client state● Open access↗
FA-23357

Hydration snapshot reconciliation: Hydration completion is attributed to another root · case 02

Hydration completion is attributed to another root.

Client state◈ Members↗
FA-23358

Hydration snapshot reconciliation: Hydration completion is attributed to another root · case 03

Hydration completion is attributed to another root.

Client state◈ Members↗
FA-23359

Hydration snapshot reconciliation: Hydration completion is attributed to another root · case 04

Hydration completion is attributed to another root.

Client state◈ Members↗
FA-23360

Hydration snapshot reconciliation: Hydration completion is attributed to another root · case 05

Hydration completion is attributed to another root.

Client state◈ Members↗
FA-23361

Hydration snapshot reconciliation: Events replay before hydration readiness · case 01

Events replay before hydration readiness.

Client state● Open access↗
FA-23362

Hydration snapshot reconciliation: Events replay before hydration readiness · case 02

Events replay before hydration readiness.

Client state◈ Members↗
FA-23363

Hydration snapshot reconciliation: Events replay before hydration readiness · case 03

Events replay before hydration readiness.

Client state◈ Members↗
FA-23364

Hydration snapshot reconciliation: Events replay before hydration readiness · case 04

Events replay before hydration readiness.

Client state◈ Members↗
FA-23365

Hydration snapshot reconciliation: Events replay before hydration readiness · case 05

Events replay before hydration readiness.

Client state◈ Members↗
FA-23366

Hydration snapshot reconciliation: Already replayed events execute again · case 01

Already replayed events execute again.

Client state● Open access↗
FA-23367

Hydration snapshot reconciliation: Already replayed events execute again · case 02

Already replayed events execute again.

Client state◈ Members↗
FA-23368

Hydration snapshot reconciliation: Already replayed events execute again · case 03

Already replayed events execute again.

Client state◈ Members↗
FA-23369

Hydration snapshot reconciliation: Already replayed events execute again · case 04

Already replayed events execute again.

Client state◈ Members↗
FA-23370

Hydration snapshot reconciliation: Already replayed events execute again · case 05

Already replayed events execute again.

Client state◈ Members↗
FA-23371

Hydration snapshot reconciliation: Server-removed keys survive hydration · case 01

Server-removed keys survive hydration.

Client state● Open access↗
FA-23372

Hydration snapshot reconciliation: Server-removed keys survive hydration · case 02

Server-removed keys survive hydration.

Client state◈ Members↗
FA-23373

Hydration snapshot reconciliation: Server-removed keys survive hydration · case 03

Server-removed keys survive hydration.

Client state◈ Members↗
FA-23374

Hydration snapshot reconciliation: Server-removed keys survive hydration · case 04

Server-removed keys survive hydration.

Client state◈ Members↗
FA-23375

Hydration snapshot reconciliation: Server-removed keys survive hydration · case 05

Server-removed keys survive hydration.

Client state◈ Members↗
FA-23376

Hydration snapshot reconciliation: Absent dirty keys retain hydration ownership · case 01

Absent dirty keys retain hydration ownership.

Client state● Open access↗
FA-23377

Hydration snapshot reconciliation: Absent dirty keys retain hydration ownership · case 02

Absent dirty keys retain hydration ownership.

Client state◈ Members↗
FA-23378

Hydration snapshot reconciliation: Absent dirty keys retain hydration ownership · case 03

Absent dirty keys retain hydration ownership.

Client state◈ Members↗
FA-23379

Hydration snapshot reconciliation: Absent dirty keys retain hydration ownership · case 04

Absent dirty keys retain hydration ownership.

Client state◈ Members↗
FA-23380

Hydration snapshot reconciliation: Absent dirty keys retain hydration ownership · case 05

Absent dirty keys retain hydration ownership.

Client state◈ Members↗
FA-23381

Hydration snapshot reconciliation: Client-only pre-hydration data is discarded · case 01

Client-only pre-hydration data is discarded.

Client state● Open access↗
FA-23382

Hydration snapshot reconciliation: Client-only pre-hydration data is discarded · case 02

Client-only pre-hydration data is discarded.

Client state◈ Members↗
FA-23383

Hydration snapshot reconciliation: Client-only pre-hydration data is discarded · case 03

Client-only pre-hydration data is discarded.

Client state◈ Members↗
FA-23384

Hydration snapshot reconciliation: Client-only pre-hydration data is discarded · case 04

Client-only pre-hydration data is discarded.

Client state◈ Members↗
FA-23385

Hydration snapshot reconciliation: Client-only pre-hydration data is discarded · case 05

Client-only pre-hydration data is discarded.

Client state◈ Members↗
FA-23386

Hydration snapshot reconciliation: An empty snapshot remains permanently loading · case 01

An empty snapshot remains permanently loading.

Client state● Open access↗
FA-23387

Hydration snapshot reconciliation: An empty snapshot remains permanently loading · case 02

An empty snapshot remains permanently loading.

Client state◈ Members↗
FA-23388

Hydration snapshot reconciliation: An empty snapshot remains permanently loading · case 03

An empty snapshot remains permanently loading.

Client state◈ Members↗
FA-23389

Hydration snapshot reconciliation: An empty snapshot remains permanently loading · case 04

An empty snapshot remains permanently loading.

Client state◈ Members↗
FA-23390

Hydration snapshot reconciliation: An empty snapshot remains permanently loading · case 05

An empty snapshot remains permanently loading.

Client state◈ Members↗
FA-23391

Optimistic patch journal: Rejected rebase · case 01

Rejected rebase.

Client state● Open access↗
FA-23392

Optimistic patch journal: Rejected rebase · case 02

Rejected rebase.

Client state◈ Members↗
FA-23393

Optimistic patch journal: Rejected rebase · case 03

Rejected rebase.

Client state◈ Members↗
FA-23394

Optimistic patch journal: Rejected rebase · case 04

Rejected rebase.

Client state◈ Members↗
FA-23395

Optimistic patch journal: Rejected rebase · case 05

Rejected rebase.

Client state◈ Members↗
FA-23396

Optimistic patch journal: Confirmed base · case 01

Confirmed base.

Client state● Open access↗
FA-23397

Optimistic patch journal: Confirmed base · case 02

Confirmed base.

Client state◈ Members↗
FA-23398

Optimistic patch journal: Confirmed base · case 03

Confirmed base.

Client state◈ Members↗
FA-23399

Optimistic patch journal: Confirmed base · case 04

Confirmed base.

Client state◈ Members↗
FA-23400

Optimistic patch journal: Confirmed base · case 05

Confirmed base.

Client state◈ 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 ↗