Cairn
NousResearch/hermes-agent

SIGUSR2 faulthandler chaining kills gateway process

Cluster 84373 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

A bug where the SIGUSR2 signal handler for fault diagnostics chains to the default signal action, causing the Linux gateway process to be killed. Fixes address preventing this chaining behavior.

Open issues1

  • Issue#84373[Bug]: SIGUSR2 faulthandler diagnostic kills Linux gateway because handler chains to default signal action

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · superseded by another PR 1

  • #84447 fix(gateway): do not chain SIGUSR2 faulthandler to default action (#84373) · superseded by another PR → #75750
  • #84539 fix(gateway): do not chain SIGUSR2 faulthandler dump to process kill · duplicate → #75750, #84373
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.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
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/84373.json
cluster/84373.md