VSCODE terminals are automatically created without any visible reason

[axonasif]

Bug description

If you open a workspace, an extra terminal is always created by the supervisor and ide-process(on workspace-restart) with bash as the shell regardless of your default shell settings on VSCODE (I have fish as the default shell, and it does get used if I manually create a terminal)

Steps to reproduce

Please check the video below:
https://www.loom.com/share/5beb29c3548f45dcb9431f52a1e71539

Workspace affected

No response

Expected behavior

No response

Example repository

https://github.com/axonasif/test

Anything else?

cc @schickling

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[schickling]

Still an issue

[akosyakov]

Unfortunately it is standard behaviour from VS Code. If there is no any terminals, it adds our. And since our terminals are added by extensions which is loaded after VS Code Core there is always one new regular terminal from VS Code. I'm not sure how it can be easily improved without changing internals of VS Code.

[schickling]

While I agree that this should be addressed in VSC longer term, can this be worked around via some sort of script by Gitpod? This issue causes me to add a manual step everything before I'm able to use a project on Gitpod.

[axonasif]

@schickling currently I'm doing it via my dotfiles as a workaround. You can try it if you want.

All Gitpod/IDE created bash($SHELL) terminals get transferred into a global tmux session after task completion.

[schickling]

This is a very common "papercut" for me as it's a manual step when opening any workspace in Gitpod. Hopefully this gets fixed soon :)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[schickling]

Still an issue

[jeanp413]

I pushed a commit gitpod-io/openvscode-server@69d257e
@axonasif could you test it in tomorrow's insiders

[jeanp413]

Closing this for now, for now it's available in insiders, will be available in the next stable release

[schickling]

Closing this for now, for now it's available in insiders, will be available in the next stable release

What's the rough ETA for this?

[jeanp413]

What's the rough ETA for this?

first week of February

For insiders, you can set it in your preferences