Terminal became unresponsive, telemetry output disappeared

[bamurtaugh]

Testing #167475

Version: 1.74.0-insider (user setup)
Commit: 8b98917
Date: 2022-11-29T07:05:56.358Z
Electron: 19.1.6
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.25247
Sandboxed: Yes

Steps:

• Open a GitHub repo in VS Code Insiders
• Set telemetry log level to debug
• Experiment with different git commands in terminal, attempting to test quick fixes
• After one of several git push commands, VS Code is stuck loading (SCM view doesn't show commit is pushed, status bar shows loading indefinitely)
• 🐛 Eventually get a notification that the pty host in the terminal has become unresponsive. I needed to close all open VS Code instances to get back to a working terminal
• 🐛 Though the terminal works now, I can no longer find the telemetry output channel - I've run the command to set log level and reloaded several times:

[bamurtaugh]

Seems setting the log level to trace rather than debug results in the Output channel displaying - should we be testing with trace instead?

[Tyriar]

Yes trace is right as mentioned in https://code.visualstudio.com/docs/getstarted/telemetry#_output-channel-for-telemetry-events, the TPI was wrong here.

[Tyriar]

After one of several git push commands, VS Code is stuck loading (SCM view doesn't show commit is pushed, status bar shows loading indefinitely)

Could you get a gif of this happening if possible? You might be seeing #130320?

[bamurtaugh]

If I encounter again, I'll definitely share a gif - it felt like it all happened so fast that I didn't capture a gif this time.

It does look like the issue you linked - I saw the message in #130320 (comment).

[meganrogge]

Sorry I meant open dev tools where Debug level shows what is sent as telemetry. Preferable to check the telemetry output channel though as Daniel clarified above

[meganrogge]

@bamurtaugh pls reopen this if you see this again