FAILURE MAP
← Case archive

FA-24174 / Client state / Member archive

Visibility-aware client polling: Inflight reconnect dedup · case 04

Inflight reconnect dedup.

Member previewVariant 4 · 3 implementations · 60 checks per implementation

Case contract

Only one poll may be in flight. Foreground polling pauses offline or hidden; a background policy permits hidden work. Missed ticks coalesce into one catch-up request and scheduling restarts relative to the current clock. Operation inflight-reconnect-dedup has the six explicit input/output oracles below.

Why this case matters

An offline client lifecycle model that isolates a state-management defect without DOM rendering or network services.

One recorded failure

Sample boundary fixture

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

Boundary fixtureActualExpectedOutcome
inflight-reconnect-dedup scenario 3truefalseFailed

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 ↗