NousResearch/hermes-agent
Dashboard process detection when --profile precedes subcommand
Cluster 44035 · hermes cli. Data as of
3 open items. Fix attempted, not merged.
The short answer
0open issues
3open PRs
11items grouped
- Known?
- Yes. 11 related items grouped here, 3 issues already closed.
- Fix event
- No fix has been merged to main. 5 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 0 issues and 3 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskMost members describe the same CLI problem: dashboard/serve processes launched with global flags such as --profile before the subcommand may not be detected by status, stop, or update sweeps. A couple of members relate this to stale runtime after update for non-default profiles, including an ImportError report, and several appear to propose changes to process matching.
Open issues0
Open PRs3
5 PRs closed without merging
From the close comments: superseded by another PR 3 · closed without comment 2
-
#44048 fix(cli): detect dashboard PIDs when --profile precedes the subcommand · superseded by another PR →
#44165 -
#44165 fix(cli): tokenized dashboard cmdline matcher — detect global flags before the subcommand · superseded by another PR →
7bf1373,#121156 -
#44206 fix(cli): detect dashboard processes when --profile precedes subcommand (#44035) · superseded by another PR →
#44165,#44035 - #44252 fix(cli): dashboard status/stop/update miss running dashboards when --profile precedes the subcommand · closed without comment
- #60606 fix(cli): reap dashboard/serve backends launched with pre-subcommand flags on update · closed without comment
Closed issues · 3
- Closed#44035[Bug]: dashboard status/update miss running dashboards when --profile appears before the subcommand
- Closed#56717[Bug]: non-default profile can keep stale runtime after update, causing ImportError
- Closed#60540hermes update leaves dashboard/serve backends running old code when launched with pre-subcommand flags (--profile <name> dashboard)
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.16: 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
- hermes cli
- Closed issues
- 3
- Attempts
- 5 PRs closed without merging