I've modified a copy of your proxy script to work with our SGE scheduler. This mostly involved swapping out the "salloc" SLURM command for "qrsh". The proxy script then works very well, with my local VS Code connecting to our login node to run qrsh. The new structure with the local override file is very convenient.
However, if in VS Code I use the "Open Folder" command the window reloads and this drops the stdin connection that the proxy script is listening on. This stops the for loop in function _stdin_proxy_fn and the proxy script closes. VS Code then re-launches the connection (with a new call to qrsh, so another wait in the queue) and will eventually open with the selected folder active. Do you have any suggestion on how to fix this behavior? What I'd like to see happen is when "Open Folder" is executed VS Code's window reload would leave the proxy running and connected to the existing remote node. Thank you!
vlog.txt
I've modified a copy of your proxy script to work with our SGE scheduler. This mostly involved swapping out the "salloc" SLURM command for "qrsh". The proxy script then works very well, with my local VS Code connecting to our login node to run qrsh. The new structure with the local override file is very convenient.
However, if in VS Code I use the "Open Folder" command the window reloads and this drops the stdin connection that the proxy script is listening on. This stops the for loop in function
_stdin_proxy_fnand the proxy script closes. VS Code then re-launches the connection (with a new call to qrsh, so another wait in the queue) and will eventually open with the selected folder active. Do you have any suggestion on how to fix this behavior? What I'd like to see happen is when "Open Folder" is executed VS Code's window reload would leave the proxy running and connected to the existing remote node. Thank you!vlog.txt