NousResearch/hermes-agent
Preserve readable non-ASCII/CJK text in cron JSON output
Cluster 26128 · cron. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
7items grouped
- Known?
- Yes. 7 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 5 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 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskMembers share one theme: cron job data (jobs.json) and cronjob tool output reportedly show Chinese/non-ASCII text as Unicode escape sequences, and several PRs propose using ensure_ascii=False or UTF-8 encoding to keep it readable. One member is an issue describing the symptom; the rest are proposed fixes with slightly different scopes.
Open issues1
- Issue#26128cronjob list/update displays Chinese text as Unicode escape sequences
Open PRs1
- PR#5859fix: add ensure_ascii=False to all json.dump calls for CJK readability
5 PRs closed without merging
From the close comments: superseded by another PR 2 · closed without comment 1 · duplicate 1 · merged via another change 1
-
#26266 fix(cron): stop escaping non-ASCII characters in jobs.json and tool output (#26128) · superseded by another PR →
#26128,#5859,#26266 -
#26556 fix(cron): use ensure_ascii=False for CJK text in cronjob output · superseded by another PR →
#5859,#26266,#24880,#18785 -
#27456 fix(cron): preserve non-ASCII characters in jobs.json · duplicate →
#5859,#18785,#24880,#26266,#26556 -
#29754 fix: ensure utf-8 encoding in jobs.json · merged via another change →
#81962 - #121853 fix(cron): preserve readable Unicode in tool responses (salvage #26266) · closed without comment
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.29: 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 LabAt a glance
- Subsystem
- cron
- Closed issues
- 0
- Attempts
- 5 PRs closed without merging