NousResearch/hermes-agent

venv-blocker scan timeout fixes for Windows

Cluster 98377. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #99674 on 31 Aug 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #99674. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #99674, then check it covers your case.

Read #99674 Pick up a Lab task

These issues and pull requests address a problem where the venv-blocker process scan exceeds its timeout on Windows hosts with many running processes, causing update failures. Proposed approaches include raising the timeout limit, filtering processes by name before reading cmdline, and general hardening of the scan.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#99674 fix(desktop): prevent venv scan timeout on busy Windows hosts (salvage #75570)

merged to main

files: apps/desktop/electron/main.ts, apps/desktop/electron/venv-blocker-scan.test.ts, apps/desktop/electron/venv-blocker-scan.ts, hermes_cli/update_cmd.py, tests/hermes_cli/test_update_venv_health.py

2 PRs closed without merging

From the close comments: merged via another change 2

#98521 fix(desktop): raise venv-blocker scan timeout from 15s to 60s · merged via another change → #75570, #99674, #98377
#98696 perf(update): filter venv-blocker scan by name before reading cmdline · merged via another change → #75570, #99674, #98377

Closed issues · 1

Closed#98377[Bug]: venv-blocker scan exceeds its own 15s timeout on hosts with many processes — update fails with no visible reason

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.50: 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

Merged PRs: #99674
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 31 Aug 2026

For your agent

The same facts, typed.

cluster/98377.json
cluster/98377.md