Cairn
NousResearch/hermes-agent

Fix hung pip probe blocking Windows updates

Cluster 120169 · hermes cli. Data as of

1 open item. Fix attempted, not merged.

The short answer

0open issues
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
0 issues and 1 PR.

A hung pip --version probe during the updater's post-swap dependency phase can orphan the process and block all subsequent update attempts on Windows. Two fixes address bounding the probe and preventing it from stalling later update runs.

Open issues0

No open issues.

Open PRs1

  • PR#120182fix(updater): stop hung pip checks from blocking later Windows updates

1 PR closed without merging

From the close comments: done elsewhere 1

  • #120191 fix(install): bound the venv pip probe so an update cannot orphan it · done elsewhere → 3eea0fe, 26c4e8b, 33a30fd, #120169
Closed issues · 1
  • Closed#120169[Bug]: Windows — a hung `pip --version` probe from the updater's own post-swap deps phase orphans and blocks every later `hermes update`
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

Subsystem
hermes cli
Closed issues
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/120169.json
cluster/120169.md