NousResearch/hermes-agent

Windows sysconf AttributeError in worker memory limit

Cluster 90570 · agent. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 3 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 0 PRs.

These issues and PRs address an unhandled AttributeError that occurs on Windows when os.sysconf is unavailable, specifically in the worker memory bounds logic. Multiple fix attempts approach the same cross-platform compatibility problem from slightly different angles.

Open issues1

  • Issue#90570Unhandled AttributeError in _worker_memory_max_bytes on Windows

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: duplicate 2 · other 1

  • #90577 fix(process_registry): make _worker_memory_max_bytes cross-platform and handle missing os.sysconf on Windows · other
  • #90583 fix(tools): catch absent-sysconf AttributeError in the worker memory bound · duplicate → #90577
  • #90627 fix(terminal): fall back when sysconf is unavailable · duplicate → #90577
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

Subsystem
agent
Closed issues
0
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.