-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
SSH broken when in terminal experiment #22339
Comments
@Queuecumber I've opened a new issue for you to further understand what might be causing the problem. First of all, please try the pre-release version of the extension: |
Secondly, if that doesn't work, can you describe in more details about how |
Also, reading the original issue it seems like you want SSH inside a SSH connection, do you think "Remote - SSH" extension can help you with that instead of configuring the terminal to do the SSH itself? |
Thanks for opening this, let me try to answer your questions
It looks like the change in venv activation works by changing the
Unfortunately "Remote - SSH" can't help me here. As I said in the original issue: I have to use the "Remote - SSH" extension to connect to a "Code Editing" server. From that server I have to ssh to a "Code Submission" server to run my code. I am not permitted to run the vscode server on the "Code Submission" server itself, it has to be a bare ssh session. |
I see, did you try echo'ing echo $PATH It should be possible to send environment variables over SSH, if one asks https://chat.openai.com/ it lists a few ways to do it. |
I did echo $PATH and it's not set correctly, it's a good idea to ask chat gpt about it, let me try out its suggestions and get back to you |
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off. |
Originally posted by @Queuecumber in #11039 (comment)
My existing flow was broken by this change, it would be nice if there was a setting to re-enable the explicit
source
command. I can't see another workaround to fix it but I am open to trying some things.Because of the way my server environment is setup I need to edit on a different machine than I launch my code on. To make this simpler I made a terminal like this:
this worked fine with the explicit
source
command but loses all the environment variables with the new method. I've tried a few things to set them such as adding${env:PATH}
before myzsh
command and using the ssh argument-o SendEnv=PATH
but nothing has worked so far.The text was updated successfully, but these errors were encountered: