-
-
Notifications
You must be signed in to change notification settings - Fork 390
HLS version 0.8.0 frequently stuck when saving files #1214
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
update: I can reliably reproduce this issue just by commenting out code |
@poscat0x04 that definitely can help to debug the issue, please, could you give the instructions to reproduce it (linking to the source code if possible)? |
Oh right, sorry. To reproduce:
|
I have encountered this bug these days, too. |
I could repro following above steps. |
That probably comes from Eval plugin. @poscat0x04 and @berberman, could you check whether your log messages contain something like "Parser error" or so? |
If there is no other people to do with, I will try to rewrite doctest parser in Eval Plugin with |
Your environment
Output of
haskell-language-server --probe-tools
orhaskell-language-server-wrapper --probe-tools
:haskell-language-server version: 0.8.0.0 (GHC: 8.10.3) (PATH: /nix/store/px0cwk7xl79yq4b1pvkwaxfkwaswhis1-haskell-language-server-0.8.0.0/bin/haskell-language-server) Tool versions found on the $PATH cabal: 3.2.0.0 stack: Not found ghc: 8.10.3
Which lsp-client do you use:
vscode
Describe your project (alternative: link to the project):
cabal project
Contents of
hie.yaml
:implicit hie
Steps to reproduce
I'm not sure how to reproduce this issue reliably, but it seems that this issue comes up a lot more frequently when I'm editing a file that has errors (type errors/parse errors, etc.) in it.
Expected behaviour
HLS should not stuck
Include debug information
Execute in the root of your project the command
haskell-language-server --debug .
and paste the logs here:Debug output:
Paste the logs from the lsp-client, e.g. for VS Code
LSP logs:
The text was updated successfully, but these errors were encountered: