Cairn
NousResearch/hermes-agent

UTF-8 encoding issues in Windows migration

Cluster 8901 · hermes cli. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

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

These members address UnicodeDecodeError crashes and encoding compatibility problems encountered during OpenClaw migration on Windows systems with non-UTF-8 locales. Both a bug report and related fixes are represented.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · superseded by another PR 1

  • #9145 fix(migration): handle non-UTF-8 files in OpenClaw migration · duplicate → #8898, #71078
  • #13593 fix(encoding): add UTF-8 encoding for Windows compatibility (#7537, #8901, #7058) · superseded by another PR → #13986
Closed issues · 1
  • Closed#8901OpenClaw migration crashes with UnicodeDecodeError on Windows (non-UTF-8 locale)
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
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/8901.json
cluster/8901.md