Skip to content

[bug] Terminal Output Corruption (Garbled CJK Characters) and Layout Glitches during Heavy Usage #3527

Closed as duplicate

Description

@NEO1717

Hi Superset Support Team,

Image

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!

Activity

  1. added a commit that references this issue on Apr 17, 2026
  2. Kitenite commented on May 6, 2026

    @Kitenite
    Member

    Related reports (cross-referenced during issue triage — same area, may or may not share a root cause):

  3. hanqyu commented on May 15, 2026

    @hanqyu

    It really bothers me. Any updates for fixing this?

  4. jnelken commented on May 19, 2026

    @jnelken
  5. Kitenite commented on Jul 11, 2026

    @Kitenite
    Member

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions