Cairn
NousResearch/hermes-agent

Non-UTF-8 file encoding handling in writes and edits

Cluster 121982 · agent. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues 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
1 issue and 1 PR.

These items address a bug where text inserted into non-UTF-8 files is written as UTF-8 without error, and propose fixes to either write in the file's own encoding or refuse operations that would leave a file with mixed encodings.

Open issues1

  • Issue#121982[Bug]: a file edit writes inserted text as UTF-8 into a non-UTF-8 file and reports success (write half of #120514)

Open PRs1

  • PR#124810fix(tools): refuse an edit that would leave a file in two encodings

1 PR closed without merging

From the close comments: stale or abandoned 1

  • #124110 fix(file-ops): write a non-UTF-8 file in its own encoding, or refuse · stale or abandoned
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
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/121982.json
cluster/121982.md