Gateway startup sweep incorrectly prunes recovered session routes
Cluster 95957. Data as of
Nothing open on GitHub. Fix merged in #96428 on 27 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #96428. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #96428. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where the gateway's startup recovery process removes sessions.json entries or routes even when session recovery succeeds with the same session ID. The fix ensures that only routes with a different session ID trigger repointing or pruning.
Open issues0
Open PRs0
Fixes on record
-
#96428 fix(gateway): keep sessions.json route when startup recovery succeeds with the same session id (salvage #95963)
files:
gateway/session.py,tests/gateway/test_session_store_stale_prune.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#95963 fix(gateway): keep sessions.json entry when startup recovery succeeds with same session id · merged via another change →
#96428
Closed issues · 1
- Closed#95957Gateway startup sweep prunes routes whose session recovery SUCCEEDED — repoint branch only fires on a different session id
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.67: 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
- #96428
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 27 Aug 2026