NousResearch/hermes-agent
Orphan dashboard process causes persistent code-skew 503
Cluster 101561 · apps/desktop. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
4items grouped
- Known?
- Yes. 4 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 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab task
A leftover dashboard process that outlives a failed or skipped hermes update triggers a persistent 503 code-skew error blocking the model picker. The associated fixes address reaping the orphaned PID and improving platform-aware hints and launchd restart behavior.
Open issues1
- Issue#101561[Bug]: Code-skew guard permanently blocks the model picker (503) when the dashboard process outlives a failed/never-run `hermes update`
Open PRs1
- PR#128316fix(desktop): reap the leftover dashboard pid that serves the code-skew 503 (#101561)
2 PRs closed without merging
From the close comments: stale or abandoned 1 · superseded by another PR 1
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
- apps/desktop
- Closed issues
- 0
- Attempts
- 2 PRs closed without merging