Rob Lourens
Rob Lourens
> Our compute nodes have the ports used by VS Code Remote SSH disabled, so there isn't an easy way around this issue. Do you mean that port forwarding for...
What code do you mean by "that code"? I don't think the issue you point to is related. We run the installer script essentially like `echo | ssh hostname bash`....
No capacity to address this in the near future but I am interested to hear how the cluster setup works for other users - if anyone is not using `slurm/srun`...
What is `$SSH_AUTH_SOCK` before you run the workaround?
Most likely you went through reconnection and are now connecting through a different ssh process, this means the original ssh auth sock is invalid. The extension tries to redirect SSH_AUTH_SOCK...
Do you have `terminal.integrated.inheritEnv` or `remote.SSH.enableAgentForwarding` disabled? Is this a terminal from a previous session that was reconnected, or a fresh terminal?
Can you share the log from the Remote-SSH output channel? Basically we should be trying to rewrite your SSH_AUTH_SOCK to something like `/tmp/vscode-ssh-auth-sock-493210776` or `/run/user/1000/vscode-ssh-auth-sock-493210776`
Probably related to https://github.com/microsoft/vscode-remote-release/issues/2349. Are you opening a large folder and what extensions are you using?
Hm, I would guess that memory is somehow the issue here even though you say it doesn't seem to be using a lot.
Your report is concerning but I can't reproduce it. I work with vscode remote frequently on an ubuntu cloud VM with an uptime of almost a year. I would need...