bash.ts: hardcoded UTF-8 decoding produces garbled output on non-UTF-8 systems #30869

Activity

1. github-actions

   assigned

   rekram1-node

   on Jun 5, 2026
2. github-actions commented on Jun 5, 2026

   

   github-actionsBot

   on Jun 5, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • Windows CJK characters garbled in bash tool output #24080: Same issue — Windows CJK characters garbled in bash tool output (closed, same file and root cause)
   • fix: PowerShell output encoding for non-ASCII characters on Windows #23636: Related open issue — PowerShell output encoding for non-ASCII characters on Windows (same Windows GBK/CJK context)
   • Encoding issue: non-UTF-8 encoded files on Windows [I find a solution] #30187: Related closed issue — Encoding issue with non-UTF-8 files on Windows in a different tool

   Please review those issues and, if your issue is distinct, clarify how it differs.
6. skywalker-35 commented on Jun 16, 2026

   

   skywalker-35

   on Jun 16, 2026

   More actions

   Same issue here on Chinese Windows (code page 936/GBK). The bash tool hardcodes result.stdout.toString("utf8") at line 173 in bash.ts, but Windows system commands output in the system's active code page (GBK on zh-CN). The simple fix would be to detect the system encoding on Windows via chcp.com and use the appropriate decoder.

   Related issues: #31187, #26882, #31830, #31765

   Many Chinese/Japanese/Korean Windows users are affected by this. Please consider fixing it in an upcoming release. Thanks!