Per-profile gateway visibility in dashboard and status API
Cluster 69143 · dashboard. Data as of
Nothing open on GitHub. Fix merged in #71007 on 24 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #71007. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A regression in 0.19.0 caused dashboard widgets and the /api/status endpoint to incorrectly report per-profile s6 gateways as stopped or disconnected. These members address detecting and surfacing the correct running state for profile-specific gateways.
Open issues0
Open PRs0
Fixes on record
-
#71007 fix(web): resolve per-profile gateway state for ?profile= in /api/status
files:
hermes_cli/web_server.py,tests/hermes_cli/test_web_server.py,tests/hermes_cli/test_web_server_profile_unification.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#69143[Bug]: Dashboard machine-level status blind to s6 per-profile gateways — widget/System/Channels report "stopped"/"disconnected" while profile gateway runs (0.19.0 regression)
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.50: 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
- dashboard
- Merged PRs
- #71007
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 24 Jul 2026