-
-
Notifications
You must be signed in to change notification settings - Fork 391
HLS stops with "Assertion failed" (cleaning ghcide/hie-bios cache fixes it) #1882
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
FWIW, if I move the files to a different folder, the error ☝🏼 goes away and HLS works fine. Maybe this is some VS Code cache issue? I tried to clear all the caches in VS code that I knew how to. |
@bsaul I had this problem, too, and I had no idea where to look. Based on your suggestion above, I found |
@ttuegel Thanks! It looks like I already deleted my old directory, but I went ahead cleared that cache. |
maybe the connection between the error a removing the cache is not obvious but i think a |
@jneira that would be great. |
Closing as old and quiet |
Your environment
Output of
haskell-language-server --probe-tools
orhaskell-language-server-wrapper --probe-tools
:haskell-language-server version: 1.1.0.0 (GHC: 8.10.4) (PATH: /Users/bsaul/.ghcup/bin/haskell-language-server-wrapper-1.1.0) (GIT hash: f1c096927186a93d8e3ccd4fe8385cc1b070350b) Tool versions found on the $PATH cabal: 3.4.0.0 stack: Not found ghc: 8.10.4
Which OS do you use: MacOS
Which lsp-client do you use: VS code
Describe your project (alternative: link to the project): https://hackage.haskell.org/package/hasklepias
Contents of
hie.yaml
: none, using implicit hie.Steps to reproduce
Open a
.hs
file in VS Code.Expected behaviour
HLS to startup without error.
Actual behaviour
The following message pops up.
cabal build
andcabal repl
work without error. Also, I went back in git history to when I know HLS worked fine, and the same error comes up.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: