Skip to content

VSCode Integration does not work. #72

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
TroyKomodo opened this issue Apr 16, 2025 · 1 comment · Fixed by #73
Closed

VSCode Integration does not work. #72

TroyKomodo opened this issue Apr 16, 2025 · 1 comment · Fixed by #73

Comments

@TroyKomodo
Copy link

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.

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).

@TroyKomodo TroyKomodo changed the title VSCode Integration Does not work. VSCode Integration does not work. Apr 16, 2025
@asharkhan3101
Copy link
Collaborator

A new release 0.11.6 with a fix for this is on the way. As a fix, I ignore any unknown CLI flags instead of failing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants