Cairn
NousResearch/hermes-agent

Handling RuntimeError from Path.expanduser in agent

Cluster 43963 · agent. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

Multiple bug reports and fixes addressing an unhandled RuntimeError raised by Path.expanduser() when $HOME is unset or a nonexistent user is referenced, causing agent crashes in subdirectory hint loading.

Open issues0

No open issues.

Open PRs0

No open pull requests.

5 PRs closed without merging

From the close comments: duplicate 3 · superseded by another PR 2

  • #43970 Fix _add_path_candidate crash on ~user expanduser() RuntimeError · superseded by another PR → #29433, #43963
  • #44056 fix(agent): catch RuntimeError from expanduser() with ~nonexistent_user (#43963) · superseded by another PR → #29433, #43963
  • #44095 fix(agent): catch RuntimeError from expanduser() in subdirectory hint loader · duplicate → #43970, #44056
  • #45430 fix(agent): catch RuntimeError from Path.expanduser/home when $HOME is unset · duplicate → #29433
  • #45468 fix(agent): catch RuntimeError from Path.expanduser/home when $HOME is unset · duplicate → #29433
Closed issues · 2
  • Closed#43963[Bug]: _add_path_candidate crashes the agent turn on ~user expanduser() RuntimeError (except misses RuntimeError)
  • Closed#45401bug: subdirectory_hints.py crashes with RuntimeError when $HOME is unset
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.26: 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

Subsystem
agent
Closed issues
2
Attempts
5 PRs closed without merging

For your agent

The same facts, typed.

cluster/43963.json
cluster/43963.md