-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opening interactive shells via exec subcommand is unresponsive #799
Comments
Hi 👋 Thanks for opening a detailed issue.
Interesting that I wasn't able to reproduce the issue with
It seems like the terminal is not interpreting the pasted command correctly, and instead is printing the raw escape sequences. This could be due to a misconfiguration in your terminal settings (especially with terminal emulator) @ruffsl Does the issue reproduce only for |
I only get this issue when i use the devcontainer command found at |
@samruddhikhandale: Yes, this issue persists for those images, as well as my own custom images from
@Restraint: Good find. Yep, this only seems to exhibit itself in the binaries provided by VSCode. If if build the main branch from source, and use that CLI binary instead, the exec sub command works as expected.
Update: This issues seem to persist with with the latest CLI binaries installed with the latest version of VSCode:
|
@samruddhikhandale any update on this? Thanks! |
In my testing, I was using the CLI installed with https://www.npmjs.com/package/@devcontainers/cli. No wonder I wasn't able to reproduce 😅 Thanks @Restraint for pointing out that difference. @chrmarti Do you know why the CLI behaves differently when installed with NPM versus when it is available in the VS Code library? I wonder if the binaries people are referring to are installed via the Dev Containers Extension, where there might be some special casing with VS Code. @Restraint @ruffsl Can you both use https://www.npmjs.com/package/@devcontainers/cli to unblock yourselves? Using the CLI installed with the NPM package should ideally be the right way of consuming the CLI. Thanks! |
This appears to be a bug in the wrapper we have in the Dev Containers extension. |
Update: Issues still persists with with the latest CLI binaries installed with the latest version of VSCode:
|
When attempting to open an interactive shell session via the
devcontainer exec
sub-command, the resulting shell becomes unresponsive after invoking the first command in that shell, as can be viewed via this screen recording:simplescreenrecorder-2024-04-12_09.04.59.mp4
Steps to Reproduce:
$(pwd)/.devcontainer/devcontainer.json
devcontainer build
devcontainer up
devcontainer exec whoami
to test that container is running withvscode
printed to stdoutdevcontainer exec bash
or usesh
to spawn an interactive shellNote: when attempting to paste commands via
CRTL+SHIT+V
or move the cursor, one can view the raw escape sequence values for bracketed paste mode or arrow keys presses rendered on the client shell.The text was updated successfully, but these errors were encountered: