Cairn
NousResearch/hermes-agent

Gateway zombie PIDs incorrectly treated as live lock holders

Cluster 18822 · gateway. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
9items grouped
Known?
Yes. 9 related items grouped here, 3 issues already closed.
Fix event
No fix has been merged to main. 6 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

Multiple issues and fix attempts address a bug where gateway scoped locks held by zombie processes (state Z) are not detected as stale, causing deadlocks and blocking reconnects. The cluster represents iterative efforts to make zombie PID detection correctly release stale locks.

Open issues0

No open issues.

Open PRs0

No open pull requests.

6 PRs closed without merging

From the close comments: done elsewhere 3 · superseded by another PR 2 · duplicate 1

  • #18832 fix(gateway): treat zombie PIDs as stale in scoped locks · superseded by another PR → #22427
  • #19474 fix(gateway): replace zombie scoped lock owners · done elsewhere → acca526, #18832
  • #26652 fix(gateway): treat zombie processes as stale in scoped lock detection · done elsewhere → acca526
  • #26756 fix(gateway): treat zombie scoped lock holders as stale · done elsewhere → acca526
  • #32673 fix(gateway): treat zombie processes as stale in acquire_scoped_lock · superseded by another PR → #26652
Show 1 more
  • #32702 fix: detect zombie processes in acquire_scoped_lock + allow macOS temp dir in path guard · duplicate → #18822, #32661, #26652, #18832, #22427, #24193, #24598, #32681
Closed issues · 3
  • Closed#18822Gateway scoped locks treat zombie owner PIDs as live, blocking Telegram/Slack reconnect
  • Closed#26651Gateway restart deadlocks on zombie-held scoped lock
  • Closed#32661acquire_scoped_lock: zombie processes (state Z) not detected as stale, causing false lock conflicts
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.22: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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

At a glance

Subsystem
gateway
Closed issues
3
Attempts
6 PRs closed without merging

For your agent

The same facts, typed.

cluster/18822.json
cluster/18822.md