-
Notifications
You must be signed in to change notification settings - Fork 200
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
Haskell extension hangs in VSCode #1209
Comments
Thanks for creating this issue 👍 I think quite a few people already reported similiar problems on Slack. Maybe you could also open an issue on the Haskell Language Server, linking back to this issue? I think we should definitly also have this issue on the IHP issue tracker here as it's affecting the overall experience, but likely the HLS devs can do more to fix this issue :) |
I experience this on WSL2 but interestingly not MacOS. Same project but it works very quick on macOS but takes 5+ minutes on WSL2. Just adding my experience here too |
I have similar experience. It works fine on Mac but HLS takes a lot of time to start on WSL2. I even tried to disable some HLS plugins (like Wingman) but that didn't help for me. |
I have this issue while actually booting ubuntu without any virtualization, so it may not be only an issue with WSL |
It would be nice if everyone of you could file an issue at https://github.com/haskell/haskell-language-server with the details you shared here :) Maybe you can also link to this issue here from the HLS repo issue |
Closing this as it looks like the issue is fixed with v0.18 :) feel free to reopen if you stumble across new issues with HLS. |
Here is a log.
The troubleshooting guide didn't help. |
Thanks for reporting. Maybe you could open an issue on the Haskell Language Server repo? Likely the HLS people can do more to fix the issue. |
When using IHP, either locally inside a WSL2 distro or via a Gitpod instance, the Haskell extension in VSCode hangs for a lot of time before becoming operational. For me, it's usually 4 minutes or so but a friend of mine on a weaker PC reported loading times up to 20-30 minutes.
I've provided some logs below.
Some of the actions that seem to have taken a lot of time are:
Wingman.getMetaprogramsAtSpan.TypeCheck (took 2m17s)
Wingman.codeLensProvider.GetBindings (took 3m34s)
RefineImports (took 3m34s)
When I'm using stack to manage my own Haskell projects, the extension seems to work fine and near instantaneously. Admittedly those projects are far smaller and have fewer files and everything... but ~4 minutes still seems very excessive to me.
Would be curious if anyone had similar issues and whether there might be a fix to speed things up.
Click to expand log
The text was updated successfully, but these errors were encountered: