Description
When using the "Open Terminal in Container" feature from the OpenShift Toolkit extension, the terminal is flooded with spdystream library debug log messages (log.go:245). These messages are written to the same terminal output as the interactive shell, making the terminal completely unusable — every keystroke triggers a burst of log lines that overwrite and interleave with the shell prompt and input.
Steps to Reproduce
- Install the OpenShift Toolkit extension for VS Code
- Connect to an OpenShift cluster
- In the Application Explorer, right-click a container and select "Open Terminal in Container"
- Wait for the shell to start
- Try typing any command in the shell
Expected Behavior
A clean interactive shell session in the container, with no debug output interfering with the terminal.
Actual Behavior
The terminal is immediately flooded with Go klog INFO-level messages from the spdystream SPDY transport library. Every keystroke triggers additional log lines, making the shell completely unusable. The messages look like this:
I0422 09:35:17.306321 127347 log.go:245] (0xc001124000) (0xc0008d81e0) Create stream
I0422 09:35:17.306360 127347 log.go:245] (0xc001124000) (0xc0008d81e0) Stream added, broadcasting: 1
I0422 09:35:17.329036 127347 log.go:245] (0xc001124000) Reply frame received for 1
I0422 09:35:17.329047 127347 log.go:245] (0xc001124000) (0xc0008d8280) Create stream
I0422 09:35:17.329050 127347 log.go:245] (0xc001124000) (0xc0008d8280) Stream added, broadcasting: 3
I0422 09:35:17.345576 127347 log.go:245] (0xc001124000) Reply frame received for 3
I0422 09:35:17.345587 127347 log.go:245] (0xc001124000) (0xc00118a1e0) Create stream
I0422 09:35:17.345591 127347 log.go:245] (0xc001124000) (0xc00118a1e0) Stream added, broadcasting: 5
I0422 09:35:17.362300 127347 log.go:245] (0xc001124000) Reply frame received for 5
I0422 09:35:17.362330 127347 log.go:245] (0xc001124000) (0xc00117c3c0) Create stream
I0422 09:35:17.362346 127347 log.go:245] (0xc001124000) (0xc00117c3c0) Stream added, broadcasting: 7
I0422 09:35:17.379163 127347 log.go:245] (0xc001124000) Reply frame received for 7
I0422 09:35:17.379309 127347 log.go:245] (0xc00117c3c0) (7) Writing data frame
I0422 09:35:17.383702 127347 log.go:245] (0xc001124000) Data frame received for 5
I0422 09:35:17.383718 127347 log.go:245] (0xc00118a1e0) (5) Data frame handling
I0422 09:35:17.405622 127347 log.go:245] (0xc001124000) Data frame received for 5
I0422 09:35:17.405640 127347 log.go:245] (0xc00118a1e0) (5) Data frame handling
I0422 09:35:17.405652 127347 log.go:245] (0xc00118a1e0) (5) Data frame sent
The stream IDs (1, 3, 5, 7) correspond to the SPDY streams created for stdin, stdout, stderr, and terminal resize during oc exec. These log messages appear on every single interaction (keystroke, prompt redraw, etc.).
Description
When using the "Open Terminal in Container" feature from the OpenShift Toolkit extension, the terminal is flooded with
spdystreamlibrary debug log messages (log.go:245). These messages are written to the same terminal output as the interactive shell, making the terminal completely unusable — every keystroke triggers a burst of log lines that overwrite and interleave with the shell prompt and input.Steps to Reproduce
Expected Behavior
A clean interactive shell session in the container, with no debug output interfering with the terminal.
Actual Behavior
The terminal is immediately flooded with Go
klogINFO-level messages from thespdystreamSPDY transport library. Every keystroke triggers additional log lines, making the shell completely unusable. The messages look like this:The stream IDs (1, 3, 5, 7) correspond to the SPDY streams created for stdin, stdout, stderr, and terminal resize during
oc exec. These log messages appear on every single interaction (keystroke, prompt redraw, etc.).