4 ms·
Probably one or two years ago I randomly met this wonderful tool amidst dealing with a VSCode Remote SSH problem via search. The story begins with using VSCode
by chazeon 5y ago
Probably one or two years ago I randomly met this wonderful tool amidst dealing with a VSCode Remote SSH problem via search. The story begins with using VSCode remote SSH on a HPC that is running CentOS 6. VSCode Remote SSH ship with a Node binary that is dynamically linked to a glibc that is not supported on older OSes such as CentOS 6 https://code.visualstudio.com/docs/remote/linux https://code.visualstudio.com/docs/remote/linux . I am not the system manager on the HPC and could not update the system myself, and VSCode team is too arrogant to support those old OSes. Alhough I have a homebrew environment and has a new glibc built there, the Node VSCode does not recognize that from environment variable. Manually update string in the node binary’s strings does provide me with solution at least: https://github.com/microsoft/vscode-remote-release/issues/103#issuecomment-552593089 https://github.com/microsoft/vscode-remote-release/issues/10...
As a researcher I am really thankful of the developer who created this wonderful tool.
- chazeon 5y agoAlso another reason I have to come up with this is though VSCode is open-sourced, VSCode’s remote SSH extension is private. I had to look into the extension module’s uglified source code to figure out what is happening out there… Alternative solution would involve edit the uglified js file https://github.com/microsoft/vscode-remote-release/issues/103#issuecomment-552167999 https://github.com/microsoft/vscode-remote-release/issues/10...