NousResearch/hermes-agent

Update command dashboard reap scoping bug on Windows

Cluster 118154. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue 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
Nothing open on GitHub.

These items concern a TypeError surfaced during the post-update dashboard PID reap step, where an older updater interpreter lacks the 'scope_home' parameter. The group covers the bug report and two related fixes targeting that failure mode.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #118173 fix(update): fail closed when the mixed-version reap cannot scope by home · superseded by another PR → 94ced1a, #117305, #118154
  • #120264 fix(update): run the post-update dashboard reap in a fresh interpreter when the updater predates the pull (#118154) · superseded by another PR → 94ced1a, #117305, #118154
Closed issues · 1
  • Closed#118154Update fails with TypeError: _find_stale_dashboard_pids() got an unexpected keyword argument 'scope_home' although the code updated successfully (Windows, git install)
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.00 means 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

At a glance

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.