You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[bug] Terminal Output Corruption (Garbled CJK Characters) and Layout Glitches during Heavy Usage #3527
I am experiencing severe rendering issues with the built-in terminal in Superset. When my AI agent handles extensive queries or generates a large volume of text, the CLI output becomes heavily garbled (Mojibake) and the layout breaks completely.
Description of the Issue:
As shown in the attached screenshot, when there is a fast or massive stream of data, the terminal fails to render Traditional Chinese (CJK) characters properly. The characters are corrupted and replaced by unreadable symbols (e.g., "⍰"). Additionally, the terminal UI often suffers from visual glitches, output truncation, and incorrect text alignment during these long-running tasks.
Steps to Reproduce:
Open a workspace in Superset.
Run an AI agent or a task that generates a massive amount of output (especially containing CJK/Traditional Chinese characters).
Wait for the terminal to process the stream.
Observe the terminal output becoming corrupted and the layout breaking down.
Expected Behavior:
The terminal should correctly parse and stream Unicode/UTF-8 characters without garbling, and maintain a stable layout even during heavy output generation.
I have attached a screenshot for your reference. Could you please look into this streaming and rendering issue? Thank you!
Reacted by Tobias Karlsson, y.takahashi, Geoffrey Bourne and KyuJoo Han
Closing as a duplicate of #5605, the consolidated tracker for stale terminal-rendering issues from the July 2026 stale-issue sweep (no activity since 2026-06-01). If this still applies on a current build, comment on #5605 and we'll reopen.
Activity
fix: solve #3527 — preserve surrogate pairs in terminal write chunking
fix(desktop): raise Chromium WebGL context cap to 256 (#3834)
Kitenite commentedon May 6, 2026
Related reports (cross-referenced during issue triage — same area, may or may not share a root cause):
hanqyu commentedon May 15, 2026
It really bothers me. Any updates for fixing this?
jnelken commentedon May 19, 2026
Kitenite mentioned it's an xterm issue. Please comment and vote this potential fix:
fix(desktop): bump @xterm/* to beta.220 for upstream WebGL atlas-merg…
Kitenite commentedon Jul 11, 2026
Closing as a duplicate of #5605, the consolidated tracker for stale
terminal-renderingissues from the July 2026 stale-issue sweep (no activity since 2026-06-01). If this still applies on a current build, comment on #5605 and we'll reopen.