restored terminal from browser reload may append 2R0;276;0c some times

[futurist]

OS/Web Information

• Web Browser: Chrome
• Local OS: MacOS 10.15
• Remote OS: Debian9
• Remote Architecture: x64
• code-server --version: 3.10.2

Steps to Reproduce

1. Open Terminal
2. Run some random commands
3. Reload Tab, wait for terminal restore
4. The restored terminal may append 2R0;276;0c some times.

Expected

Terminal should keep as is when restored after a reload

Actual

Sometimes there's some chars appeared in terminal.

Screenshot

Notes

This issue can be reproduced in VS Code:No

[futurist]

Also observed that the chars will be appended continually in many terminals(even it's not in front focus) for every time tab refreshing, as below image:

Above image is a hidden terminal not in front, after switched into it, found above image.

[futurist]

When using dash as shell, the extra chars will be below:

[greyscaled]

Bump, I've noticed this (within the Coder product)

[xiaoice]

Have you solved it? I have a similar problem in the form of characters [%]

[icy-fish]

Just facing the same issue with code-server version 3.10.2, envirionment infomation on my side list below:

OS/Web Information

• Web Browser: Chrome
• Local OS: Windows 10
• Remote OS: SUSE Linux Enterprise Server 12 SP5(Docker container)
• Remote Architecture: x64
• code-server --version: 3.10.2

Steps to Reproduce

1. Open Terminal(tried bash, zsh)
2. Run any commands with output
3. Leave it alone for a while(about 10 minutes)
4. Reload window, wait for terminal restore
5. The restored terminal may append 2R0;276;0c some times.

This issue also happends on other code-server instances with different shell configs and environment variables, so I don't think it's a env specified issue.

[icy-fish]

Hi @vapurrmaid , it's there any suggestion for this issue? I found something relevant which points out that some extra may need be done with xterm.js:

• https://github.com/sagemathinc/cocalc/issues/1269
• https://github.com/sagemathinc/cocalc/issues/3277

But I'm not sure what code-server can do on this scenario, could you please take a look and confirm, thanks.

[scottmudge]

Any solutions to this? Not a super problematic issue to go up a line and erase the previous command, but it's quite annoying.

[jsjoeio]

@scottmudge what version of code-server are you using? And can you reproduce it in Codespaces or Gitpod?

[scottmudge]

code-server: 3.10.2 vs code: 1.56.1

Unfortunately I am just a user of this deployment and do not admin rights to upgrade or deploy different services. Was hoping there might be a way to correct the issue from a configuration/user-space side of things.

[jsjoeio]

Hmm...that's pretty old. You might be able to play with terminal GPU rendering or something in the VS Code settings. I'm not sure what else would work unfortunately 😢

[jerch]

This happens, if the recorded terminal data contains requests, which the terminal will respond to (here DA2).

To fix that - replay first on the new terminal, then connect to the PTY. This way the responses get not sent again to the PTY.

[Bona-ai]

This happens, if the recorded terminal data contains requests, which the terminal will respond to (here DA2).

To fix that - replay first on the new terminal, then connect to the PTY. This way the responses get not sent again to the PTY.

Have you solved it? How to do it? Looking forward to your reply

[jerch]

No I have not solved it, as I dont had the issue. I've posted here, because we got a similar question in the xterm.js repo.

[code-asher]

We are closing out old issues, but let me know if this is still an issue. It seems unlikely to be in code-server though, all the replay logic is in VS Code core.