Gateway inbound gate wedged by startup-restore replay error
Cluster 116514. Data as of
Nothing open on GitHub. Fix merged in #116654 on 20 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #116654. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116654. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs concern a bug where a single failing or raising replay during startup-restore causes the gateway's inbound latch/gate to remain permanently closed. The work focuses on ensuring the gate is released even when restore fails.
Open issues0
Open PRs0
Fixes on record
-
#116654 fix(gateway): one raising startup-restore replay no longer wedges the inbound gate (#116514, salvage #116516)
files:
gateway/run_startup.py,tests/gateway/test_restart_resume_pending.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#116514One raising startup-restore replay wedges the inbound gate closed forever
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #116654
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 20 Sep 2026