Cross-profile gateway --replace conflict guard
Cluster 89315 · gateway. Data as of
Nothing open on GitHub. Fix merged in #93768. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #93768. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #99673. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a scenario where creating or replacing a gateway in one profile could terminate gateways belonging to other profiles. The changes add ownership verification and cross-profile guards around the --replace flag to prevent unintended SIGTERM across profile boundaries.
Open issues0
Open PRs0
Fixes on record
-
#93768 fix(gateway): refuse --replace when target ownership cannot be proven
files:
gateway/run.py,tests/gateway/test_replace_child_reap.py,tests/gateway/test_runner_startup_failures.py,tests/test_89315_replace_ownership_guard.py -
#99673 fix(profiles): profile delete refuses to kill another profile's gateway (#89315)
files:
gateway/status.py,hermes_cli/profiles.py,tests/hermes_cli/test_cross_profile_kill_refusal.py
2 PRs closed without merging
From the close comments: merged via another change 2
Closed issues · 1
- Closed#89315Desktop 'new profile' creates gateway that kills other profiles' gateways (--replace cross-profile SIGTERM + Feishu scoped lock conflict)
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.40: 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