FA-29797 / HTTP retries / Member archive

GOAWAY retry admission: Reconnect streams violates retry transition semantics · case 02

Reconnect streams violates retry transition semantics

Member previewVariant 2 · 3 implementations · 7 checks per implementation

Case contract

open(stream ID,replayable) records a live stream. goaway(last ID) monotonically lowers the accepted stream boundary. fail(id) retries only replayable streams above the known boundary (known unprocessed), otherwise reports ambiguous; unknown/already-finished streams are ignored. succeed closes a stream. New streams after GOAWAY are blocked. reconnect resets connection boundary and stream IDs while retaining decision history.

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	`[["duplicate", "retry"], 0]`	`[["unreplayable"], 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.