Gateway lifecycle guard bypass when self-targeting profile
Cluster 78028 · cron. Data as of
Nothing open on GitHub. Fix merged in #93291 on 23 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 #93291. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #93291. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs concern a bug where using the profile flag to target the gateway's own profile causes restart and stop commands to bypass the lifecycle guard. The work focuses on identifying and fixing this self-targeting bypass.
Open issues0
Open PRs0
Fixes on record
-
#93291 fix: profile-flag gateway restart no longer bypasses the lifecycle guard when self-targeting (#78028, salvage #78044)
files:
cron/lifecycle_guard.py,tests/hermes_cli/test_gateway_restart_loop.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#78044 fix(cron): block profile-flag gateway restart/stop when self-targeting (#78028) · merged via another change →
c595d35,#93291
Closed issues · 1
- Closed#78028lifecycle_guard: hermes -p <profile> gateway stop|restart bypasses the gateway lifecycle guard
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
- Subsystem
- cron
- Merged PRs
- #93291
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 23 Aug 2026