Cron script stdout encoding fixes for Windows
NousResearch/hermes-agent · cluster 38633 · cron
Data as of
Nothing open on GitHub. Fix merged in #70875. Check it covers your case.
The short answer
- Known?
- Yes. 8 related items grouped here, 3 issues already closed.
- Fix event
- A fix was merged to main in PR #70875. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address bugs in cron's _run_job_script where subprocess stdout was silently dropped or decoded using the platform default encoding (e.g. cp1252, GBK) instead of UTF-8, particularly on Windows with pythonw.exe. Multiple fix attempts target explicit UTF-8 encoding and reliable stdout capture on non-UTF-8 Windows locales.
Open issues0
Open PRs0
Fixes on record
-
#70875 fix(windows): close out the text-mode subprocess decode bug class — salvage #55339/#60741/#60751 + full sweep + linter
files:
agent/anthropic_adapter.py,agent/context_references.py,agent/copilot_acp_client.py,agent/lsp/install.py,agent/proxy_sources/iron_proxy.py,agent/secret_sources/base.py,agent/secret_sources/bitwarden.py,agent/shell_hooks.py,agent/skill_preprocessing.py,agent/trace_upload.py,agent/transports/codex_app_server.py,batch_runner.py,cli.py,contributors/emails/[redacted:email],contributors/emails/[redacted:email],gateway/platforms/base.py,gateway/platforms/webhook.py,gateway/platforms/webhook_filters.py,gateway/run.py,gateway/shutdown_forensics.py(+72 more)
4 PRs closed without merging
From the close comments: closed without comment 1 · done elsewhere 1 · superseded by another PR 1 · other 1
- #38666 fix(cron): make _run_job_script work on Windows pythonw.exe + non-UTF-8 locales · closed without comment
- #42390 fix(cron): add explicit utf-8 encoding for subprocess stdout capture · other
-
#42805 fix(cron): decode no-agent script output as UTF-8 · superseded by another PR →
7498eae -
#43857 fix(cron): explicit UTF-8 encoding for script stdout capture · done elsewhere →
#70875
Closed issues · 3
- Closed#38633Windows: Two bugs in cron `_run_job_script` — pythonw.exe loses stdout + GBK encoding crash
- Closed#42384`no_agent` cron script stdout silently dropped on Windows (pythonw gateway) when output contains emoji / multi-byte UTF-8
- Closed#42785cron no_agent script stdout decoded with platform default (cp1252 on Windows), mangling non-ASCII output before delivery
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.35: 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
- Merged PRs
- #70875
- Closed issues
- 3
- Attempts
- 4 PRs closed without merging
- Fix link checked
- 24 Jul 2026