You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm writing an LSP extension that uses socket transport kind.
When the command in the server option exits with a nonnull code, the LanguageClient gets stuck in start().
constserverOptions={"command": "node","args": ["-e","process.exit(42)"],transport: {kind: TransportKind.socket,port: 8080}}constclientOptions={}lspClient=newLanguageClient("MylanguageServer","My Language Server",serverOptions,clientOptions);lspClient.onDidChangeState((state)=>{conststates=["Stopped","Running","Starting"];console.log(`State change from ${states[state.oldState-1]} to ${states[state.newState-1]}`)})lspClient.start();
I expect that the start fails if the command fails.
I tried to investigate. The start() seems to be waiting for a connection before registering on the exit event of the spawned process.
The text was updated successfully, but these errors were encountered:
I'm writing an LSP extension that uses socket transport kind.
When the command in the server option exits with a nonnull code, the LanguageClient gets stuck in
start()
.I expect that the start fails if the command fails.
I tried to investigate. The
start()
seems to be waiting for a connection before registering on theexit
event of the spawned process.The text was updated successfully, but these errors were encountered: