NousResearch/hermes-agent
Windows npm path lookup errors during hermes update
Cluster 7252 · hermes cli. Data as of
Nothing open on GitHub. Fix attempted, not merged.
The short answer
0open issues
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 2 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
- Nothing open on GitHub.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskMembers report FileNotFoundError (WinError 2) on Windows when running hermes update, with npm.cmd apparently not being found. Two pull requests propose looking up the npm path in the update and post-setup flows; the fourth member is a bug report showing the same error message, with limited detail in its title.
Open issues0
Open PRs0
2 PRs closed without merging
From the close comments: closed without comment 1 · done elsewhere 1
Closed issues · 2
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.39: 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
- 2
- Attempts
- 2 PRs closed without merging