Socket GLSP Node server closing connection

[gee4vee]

I am trying to get the workflow example running in our VS Code extension as a baseline for a new visual editor we will work on. I have gotten all the client and node server code copied and compiled. However, it just hangs at the line await serverProcess.start(); during extension activation. How can I debug this further?

I am using v2.3.0 of the GLSP components.

[gee4vee]

I can now see that the GLSP server starts briefly and then terminates.

GLSP-Server: Debugger listening on ws://127.0.0.1:59020/7a9f2138-8e99-448c-9d33-eb663d751e2b
For help, see: https://nodejs.org/en/docs/inspector

extensionHostProcess.js:163
GLSP-Server: Debugger attached.

extensionHostProcess.js:163
GLSP-Server: Waiting for the debugger to disconnect...

Is there a way I can dig into this to see why?

[gee4vee]

@martin-fleck-at I was able to resolve all this by correctly using the starter project. However, I am now seeing that on occasion the node command is not found when using GlspSocketServerLauncher. I suspect this could be because I'm using nvm? Is there a way to specify the path to node? I do have node in the path in any other terminal. It appears the spawn call is not correctly inheriting the environment from the parent process.

[martin-fleck-at]

Are you referring to the childProcess.spawn here: https://github.com/eclipse-glsp/glsp-vscode-integration/blob/1686d99048f64acf2db97b34b284ce21b9514538/packages/vscode-integration/src/node/quickstart-components/glsp-socket-server-launcher.ts#L157?

That is very curious and I've not seen it happen. It seems similar issues were reported when using a CI where environment variables may be manipulated (e.g., travis-ci/travis-ci#3894) but overall we should inherit the environment from the parent process. Are you manipulating the PATH somewhere? I don't think nvm should cause the problem but I cannot say for sure. Could you output your environment variables to see if node is on the path?

[gee4vee]

@martin-fleck-at So I logged the path right before calling GlspSocketServerLauncher.start(). This is all it has:

ENV: "/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin"

Compared to the path in the VS Code terminal which among many others includes /Users/gvalenc/.nvm/versions/node/v20.17.0/bin, which is the current node version specified by nvm. I am running the extension using an extensionHost launch configuration, so it appears that VS Code is not supplying anything. Are you aware of any way to enable this in the launch config?

[gee4vee]

Never mind. For some reason a restart of VS Code fixed it. Oh well! Thank you anyway!