NousResearch/hermes-agent

Skills install/browse hangs when remote source stalls

Cluster 37008 · skills. 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 indefinite hangs in skills install and browse commands caused by stalling third-party sources (notably ClawHub) and timeout mechanisms being defeated by blocking executor shutdown or unbounded catalog walks.

Open issues0

No open issues.

Open PRs0

No open pull requests.

5 PRs closed without merging

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

  • #37029 fix(skills): prevent indefinite hang when skill source stalls during parallel search · superseded by another PR → #37008, #37267, #37178, #37396
  • #37178 fix(skills): return after timed-out source search · partial fix → 3f2a56d
  • #37267 fix: stop waiting after skills hub timeout · partial fix → 105625d, #37029
  • #37396 fix(skills): don't hang on install when a third-party source stalls · superseded by another PR → #57000
  • #38481 fix(skills): honour overall_timeout and bound ClawHub catalog walk · partial fix
Closed issues · 2
  • Closed#37008[Bug]: `hermes skills install <short-name>` can hang indefinitely when a third-party source (e.g. ClawHub) stalls
  • Closed#38459skills browse hangs indefinitely on cold cache: overall_timeout defeated by blocking ThreadPoolExecutor shutdown + unbounded ClawHub catalog walk
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
skills
Closed issues
2
Attempts
5 PRs closed without merging

For your agent

The same facts, typed.