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
error: unexpected argument '--stdio' found
Usage: protols [OPTIONS]
For more information, try '--help'.
[Error - 10:08:17 PM] Server process exited with code 2.
[Error - 10:08:17 PM] Client Protols Language Server: connection to server is erroring.
write EPIPE
Shutting down server.
[Error - 10:08:17 PM] Client Protols Language Server: connection to server is erroring.
write EPIPE
[Error - 10:08:17 PM] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: starting
at Gp.shutdown (/home/troy/.vscode-server/extensions/ianandhum.protobuf-support-1.2.1/dist/extension.js:41:8468)
at Gp.stop (/home/troy/.vscode-server/extensions/ianandhum.protobuf-support-1.2.1/dist/extension.js:41:8047)
at Gp.stop (/home/troy/.vscode-server/extensions/ianandhum.protobuf-support-1.2.1/dist/extension.js:44:30480)
at Gp.handleConnectionError (/home/troy/.vscode-server/extensions/ianandhum.protobuf-support-1.2.1/dist/extension.js:43:63)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[Error - 10:08:17 PM] Server initialization failed.
Message: write EPIPE
Code: -32099
[Error - 10:08:17 PM] Protols Language Server client: couldn't create connection to server.
Message: write EPIPE
Code: -32099
[Error - 10:08:17 PM] Restarting server failed
Message: write EPIPE
Code: -32099
[Info - 10:08:17 PM] Connection to server got closed. Server will restart.
true
error: unexpected argument '--stdio' found
from the output logs of the extension it seems that protols isnt respecting LSP spec (I think), since the argument --stdio seems to be from the vscode-languageserver project not the extension itself.
Not sure if this is within scope to support the LSP spec, however it would definitely make using this language server easier for me (and maybe others).
The text was updated successfully, but these errors were encountered:
TroyKomodo
changed the title
VSCode Integration Does not work.
VSCode Integration does not work.
Apr 16, 2025
I understand this project does not officially maintain a vscode extension however, I suspect the issue might be upstream.
It seems from the extension that
https://github.com/ianandhum/vscode-protobuf-support/blob/1504ea03e101974d49a3906ac38ceffd75a7eac9/src/protols.ts#L5-L10
they are using the official https://github.com/Microsoft/vscode-languageserver-node vscode-lsp bindings which support any server that implements the LSP protocol.
https://github.com/ianandhum/vscode-protobuf-support/blob/1504ea03e101974d49a3906ac38ceffd75a7eac9/src/protols.ts#L98-L109
They initialize it like this.
from the output logs of the extension it seems that protols isnt respecting LSP spec (I think), since the argument
--stdio
seems to be from the vscode-languageserver project not the extension itself.Not sure if this is within scope to support the LSP spec, however it would definitely make using this language server easier for me (and maybe others).
The text was updated successfully, but these errors were encountered: