-
-
Notifications
You must be signed in to change notification settings - Fork 388
Failed to initialize lsp server in vscode #2068
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
Comments
VSCode ignores |
Sorta makes you think that maybe the spec is an afterthought, doesn't it? :) |
One way or another, We'll have to fix the problem in the lsp package by making the parser less strict. And make a Hackage upload before we can put HLS 1.3.0.0 in Hackage |
I found a related issue: microsoft/vscode-languageserver-node#780, where they said So we don't need to revise lsp package. Instead, update the dependency |
Reopened as we need a release of the extension |
will do asap, I think I ve seen some strange values in the actual config and I would like to fix them |
we just have released a new version of the vscode extension, could you give a try to confirm it fixes the issue? |
Fixed for me! |
great, so I guess we can close this |
Your environment
HLS master, lsp 1.2.0.1
Which OS do you use:
NixOS
Which lsp-client do you use:
vscode 1.58.2
Describe your project (alternative: link to the project):
HLS
Actual behaviour
The server failed immediately because the field
InitializeParams.capabilities.textDocument.semanticTokens.requests
in initialize message was missing.Include debug information
The initialize request sent from my vscode client:
According to the lsp specification (https://microsoft.github.io/language-server-protocol/specifications/specification-3-17/#semanticTokensClientCapabilities), this field is not optional, but it's clear that vscode didn't send this.
The text was updated successfully, but these errors were encountered: