Gateway reconnect watcher wedge fixes after network loss
NousResearch/hermes-agent · cluster 70344
Data as of
Nothing open on GitHub. Fix merged in #70987. Check it covers your case.
The short answer
- Known?
- Yes. 7 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #70987. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #70987. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where the gateway reconnect watcher could become permanently stuck (wedged) following a fatal network-loss error or a swallowed cancellation during adapter connect. Fixes involve preventing the wedge condition and adding detach-on-timeout logic around adapter connect.
Open issues0
Open PRs0
Fixes on record
-
#70987 fix(gateway): prevent reconnect watcher wedge after network-loss fatal error
files:
gateway/run.py,tests/gateway/test_platform_reconnect.py,tests/gateway/test_runner_startup_failures.py -
#72366 fix(gateway): spawn platform reconnect watcher with task-level supervision (salvage of #71867 by @ygd58)
files:
gateway/run.py,tests/gateway/test_platform_reconnect.py
4 PRs closed without merging
From the close comments: merged via another change 4
-
#70345 fix(gateway): run adapter connect detach-on-timeout so a swallowed cancel can't wedge reconnect · merged via another change →
#71176 -
#70502 fix(gateway): prevent reconnect watcher wedge after network-loss fatal error (#70344) · merged via another change →
#71177,#71176,#70345 -
#70919 fix(gateway): prevent reconnect watcher wedge after network-loss fatal error · merged via another change →
#70987,#69880,#70344 -
#71176 fix(gateway): detach-on-timeout for adapter connect so swallowed cancel can't wedge reconnect · merged via another change →
#70987,#72366
Closed issues · 1
- Closed#70344Gateway silently deaf after generic network loss — reconnect watcher never starts post-escalation (0.19.0)
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.29: 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 Lab