-
Notifications
You must be signed in to change notification settings - Fork 131
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
v2.0.0-rc1 Task error: [-32601] no such method "workspace/didChangeWatchedFiles" #137
Comments
Hi @pgreda ,
What is it that you expect to happen here? I'm aware the old extension used to underline invalid keywords - this is something we plan to implement as part of #27
That error should be mostly harmless in this context and unrelated to the problem you're most likely describing. It just means that the language server currently lacks a way of synchronizing content of files when they get changed outside of VSCode/IDE. This would usually happen when you switch branches in git. This will be implemented as part of #15 Do you remember if you or any other program could've triggered this? i.e. anything changed files within the workspace outside of VSCode? Is there anything else I missed? |
Thank you for the clarification. I’ve jumped to 2.0.0-rc.1 due to bug #324. In 1.4.0 some/most of the syntax checking worked. I will keep my fingers crossed for #27 and #15.
When you combine the fact that the syntax is not being highlighted on warnings and errors with a verbose terraform-ls output producing an error on every keystroke the user gets the feeling that something is broken. I started troubleshooting the installation and even purged my VSCode config to start from scratch. This is a bad user experience.
No, the error is generated on every single keystroke. Best regards, PG |
Is it possible that you still have the old extension installed alongside this |
I have just double checked this (full purge). There is only LS v3.0 included in 2.0.0.rc-1 running. Maybe it’s related to the fact that I’m using it on WSL2? |
I meant the version of the VSCode extension rather than language server, which should come up in the extension list here: Also do you mind checking your VSCode settings for any options which start with
That is good to know - I'm unsure if we tested the whole setup on WSL2 yet, but in theory it should work. I can try to reproduce in a Windows VM once we rule out the conflict of extensions. |
I'm seeing the same error with v2.0.1 of the plugin under
It's the only error I can find that explains why VS Code cannot seem to save Terraform files now; it hangs on "Running 'HashiCorp Terraform' Formatter..." and won't actually save changes until I cancel that operation. After cancelling so it can save, I can then |
Generally this error should in most "happy-path" circumstances (when files don't change outside of VSCode) be informative. That said it is certainly something we plan to fix/implement.
@aprice I would say that's most likely unrelated - can you open a new issue and attach the log? Thanks. |
I've got the same issue.
|
Same issue. The language server is pretty much unusable and actively prevents development while it is enabled. |
Happening to me as well on 0.13:
|
Hi folks, We plan to re-introduce synchronization, but only once this is actually supported on the server side. See relevant planned work at |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Hi,
I'm running:
Following code:
Doesn't produce any error in VSCode on "resxvxvcx". The plugin doesn't catch any errors. Every detected change ends with following error:
The text was updated successfully, but these errors were encountered: