UnicodeEncodeError ASCII codec handling and fixes
Cluster 6843. Data as of
Nothing open on GitHub. Fix merged in #7292. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #7292. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #10537. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug report and several iterative fix attempts addressing UnicodeEncodeError failures that occur when the system runs under an ASCII locale. The fixes focus on sanitizing message content and syncing client state during error recovery.
Open issues0
Open PRs0
Fixes on record
-
#7292 fix(agent): salvage agent core PRs #6849 #6846
files:
agent/context_references.py,cli.py,run_agent.py,tests/agent/test_context_references.py,tests/run_agent/test_unicode_ascii_codec.py -
#10537 fix: complete ASCII-locale UnicodeEncodeError recovery for api_messages/reasoning_content (#6843)
files:
.mailmap,run_agent.py,scripts/release.py,tests/run_agent/test_unicode_ascii_codec.py
2 PRs closed without merging
From the close comments: merged via another change 2
Closed issues · 1
- Closed#6843[Bug]: UnicodeEncodeError
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.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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