FA-7466 / Multiplexed protocols / Open access

Http2 new stream id must increase without reuse · case 01

Http2 new stream id must increase without reuse.

Verified by executionVariant 1 · 4 checks per implementationDownload source bundle ↓JSON ↗

ROOT CAUSE

The faulty implementation uses `stream >= highest` for the http2-new-stream-id-must-increase-without-reuse decision.

THE FAILURE

The faulty implementation uses `stream >= highest` for the http2-new-stream-id-must-increase-without-reuse decision.

Unsuccessful approach: The attempted repair uses `stream == highest+2` and still violates a separate fixture.

Case contract

Bounded offline decision model: http2 new stream id must increase without reuse. Inputs are already validated protocol fields; the explicit fixtures define the supported policy, not a complete protocol implementation.

Why this case matters

This deterministic multiplexed protocols model isolates the http2-new-stream-id-must-increase-without-reuse policy at a network component boundary.

1 / The failure

Exit 1

"""Failure Map reference implementation. Python standard library only."""
import json
import ipaddress
import re
from urllib.parse import urlsplit, urljoin
N = 1
observations = []
def solve(stream, highest):
    return stream >= highest
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
_fixtures = ["check('fixture 1', solve(3, 3), False)", "check('fixture 2', solve(7, 3), True)", "check('fixture 3', solve(1, 3), False)", "check('fixture 4', solve(5, 3), True)"]
for _line in _fixtures[N % len(_fixtures):] + _fixtures[:N % len(_fixtures)]:
    exec(_line)
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)

Boundary fixture	Actual	Expected	Outcome
fixture 2	`True`	`True`	Passed
fixture 3	`False`	`False`	Passed
fixture 4	`True`	`True`	Passed
fixture 1	`True`	`False`	Failed

SHA-256 / c46986bb2ea96443a72a7c589898979f50b76b1d3216d13a5a171b9bf9c79848

2 / The unsuccessful fix

Exit 1

"""Failure Map reference implementation. Python standard library only."""
import json
import ipaddress
import re
from urllib.parse import urlsplit, urljoin
N = 1
observations = []
def solve(stream, highest):
    return stream == highest+2
def check(label, actual, expected):
    observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
_fixtures = ["check('fixture 1', solve(3, 3), False)", "check('fixture 2', solve(7, 3), True)", "check('fixture 3', solve(1, 3), False)", "check('fixture 4', solve(5, 3), True)"]
for _line in _fixtures[N % len(_fixtures):] + _fixtures[:N % len(_fixtures)]:
    exec(_line)
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)

Boundary fixture	Actual	Expected	Outcome
fixture 2	`False`	`True`	Failed
fixture 3	`False`	`False`	Passed
fixture 4	`True`	`True`	Passed
fixture 1	`False`	`False`	Passed

SHA-256 / 591146da05c67685ec6b7286522cf143699eafdc43f356a220e2c4a4de42d854

HELD IN THE MEMBER ARCHIVE

The verified repair and its recorded checks are member-only.

This mechanism has 4 recorded checks per implementation. The open-access tier publishes the failure and the unsuccessful fix; the repaired source that passes every check, and the observations that prove it, are available to members.

Every case sharing this mechanism uses the same contract and the same repair, so this one record is held back for all of them.

Member access is invitation-based. Sign in with your invited account to inspect the repair.

Verification & scope

Bounded deterministic policy model over validated inputs; not a complete protocol stack or an interoperability claim. The five variants rotate the same explicit fixture set. This reproducer isolates one failure mechanism. Results cover the supplied fixtures. Variants within a family share a test contract and should remain grouped when constructing evaluation splits. Related mechanisms with a shared evaluation_group must also remain together; these controlled models are not independent production incidents.

Observations recorded using Python 3.12.14 at 2026-09-29T14:38:12.345651+00:00.

Case digest / f9beb5772b54a53d6603d19d9d76e741afc1ef2dc0b9428d112be682d5ad8330