FAILURE MAP
← Case archive

FA-10448 / Caching / Member archive

Completion of an old flush clears a newer dirty update · case 03

Completion of an old flush clears a newer dirty update.

Member previewVariant 3 · 3 implementations · 4 checks per implementation

Case contract

Entry is [key,value,version,dirty]. Clear dirty only when flush succeeded for this exact current version; preserve all other fields.

Why this case matters

A deterministic cache state transformation. Inputs are copied or treated as immutable; no remote storage, real clock, or concurrent interleaving is simulated.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
fixture 1["a", "new", 2, false]["a", "new", 2, true]Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.

Sign in to the archive ↗