FA-30012 / HTTP retries / Member archive

Cancellation of queued retries: Finish consumption violates retry transition semantics · case 02

Finish consumption violates retry transition semantics

Member previewVariant 2 · 3 implementations · 8 checks per implementation

Case contract

schedule(id,due) replaces an existing queued retry for that ID. cancel(id) removes it and permanently cancels that logical request. poll(now) starts every due noncancelled retry ordered by due then ID and removes it before execution. finish records completion only for running retries. Cancelling running work removes running status; its late completion is ignored. Return start/finish events and pending/running IDs.

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	`[[["start", "a"], ["start", "b"], ["finish", "a"], ["finish", "a"]], [], ["a", "b"]]`	`[[["start", "a"], ["start", "b"], ["finish", "a"]], [], ["b"]]`	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.