FA-29730 / HTTP retries / Member archive

Retry after consumer-visible response delivery: Completing an empty response does not stop later attempts · case 05

Completing an empty response does not stop later attempts

Member previewVariant 5 · 3 implementations · 7 checks per implementation

Case contract

begin starts an attempt only while nonterminal, headers records a status, deliver(bytes) records irreversible delivery, fail allows retry only before any delivered bytes. A zero-byte delivery is reversible. finish terminally succeeds. cancel terminally cancels. New attempts reset their local status but never erase already exposed data. Return retry decisions and exposed byte count.

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
5	`[["success", ["retry", null]], 0]`	`[["success", "terminal", "terminal"], 0]`	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.