NousResearch/hermes-agent

handling OSError when gh CLI is not executable

Cluster 39540 · hermes cli. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
5items grouped
Known?
Yes. 5 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 2 PRs.

These issues and PRs address a crash in the hermes doctor command when the gh CLI is unavailable or not executable, such as in WSL environments pointing to gh.exe. The proposed fixes involve catching OSError and PermissionError in the _gh_authenticated function.

Open issues1

  • Issue#39540hermes doctor crashes with PermissionError when gh is unavailable (e.g. WSL pointing to gh.exe)

Open PRs2

  • PR#39545fix(cli): catch OSError in _gh_authenticated to handle PermissionError
  • PR#41837fix(cli): handle gh execution errors in doctor

2 PRs closed without merging

From the close comments: duplicate 1 · other 1

  • #39605 fix(doctor): catch OSError/PermissionError in _gh_authenticated · other → #39545, #39648
  • #39648 fix(doctor): catch OSError when gh CLI is not executable · duplicate → #39545, #39605
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.40: 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
hermes cli
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.