NousResearch/hermes-agent

Windows subprocess UTF-8 encoding bug and fixes

Cluster 97322 · hermes cli. Data as of

3 open items. Fix attempted, not merged.

The short answer

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

A bug where subprocess reader threads on Windows raised UnicodeDecodeError due to cp1252 encoding assumptions, along with two fix attempts addressing UTF-8 encoding in CLI update check subprocess calls.

Open issues1

  • Issue#97322[Bug]: UnicodeDecodeError (cp1252) in subprocess reader thread during --version / update check on Windows

Open PRs2

  • PR#97357fix(cli): handle non-cp1252 bytes in subprocess reader threads on Windows (#97322)
  • PR#97424fix(cli): add UTF-8 encoding to subprocess calls in update check
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
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.