FA-29532 / HTTP retries / Member archive

Late response fencing between retry attempts: Retry attempt identifiers are reused or skip the caller-visible generation · case 02

Retry attempt identifiers are reused or skip the caller-visible generation

Member previewVariant 2 · 3 implementations · 6 checks per implementation

Case contract

start allocates a strictly increasing generation. complete(generation,value) publishes only the current active generation and terminates it; duplicate/stale results are rejected. timeout(generation) deactivates only that generation. cancel terminates the logical request permanently. Return accepted/rejected results plus current generation and cancellation flag.

Why this case matters

Offline deterministic model of HTTP request retries.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
2	`[[["started", 1], ["started", 1], "stale", "stale"], 1, false]`	`[[["started", 1], ["started", 2], "stale", ["accepted", 7]], 2, false]`	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.