-
Notifications
You must be signed in to change notification settings - Fork 90
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
Working out the project GHC version seemingly never finishes #421
Comments
I have the same problem. |
Downgrading to the previous version of the extension solves the problem. |
What is the version you downgraded to? I was hesitant to do so because 1.3.0 and 1.4.0 seem to exist, but VS Code suggests only 1.2.0 as previous version. Actually, after upgrading VS Code to 1.58 the "Install another version" option became disabled and there is no way of restoring a working environment. |
I took a look at what should happen in the source code and running manually the following works:
|
1.4.0 is the one I downgraded to after downgrading VS Code :). Thanks for the feedback. |
Additional observations. When manually running the non-wrapper binary, much more output is produced and in the end an error is reported:
My
Given that manually running the wrapper seems to do more than the non-wrapper binary, I tried manually setting the executable path to it (and to the non-wrapper) but VS Code shows an error pop-up with
In the past I used to change this setting like this and this error is new and surprising to me. Finally, I tried deleting |
Hi, sorry for the incoveniences, i'll try to fix the code introduced in #414 and revert the change if it is not possible to do it in a reasonable amount of time. |
Just tried again and works for me in windows |
Do I understand correctly that the happy flow works, but error handling (at least under Linux) does not? |
Yeah, that is my impression, however, error handling apart, i used a way to spawn the subprocess that uses a shell by default and maybe it could be the cause of your issue (afaiu the process of getting ghc version works for you) |
@Savelenko @gboduljak hi, i've made a pr to try to fix the issue, coud you have the chance of trying it locally to see if it really fixes the issue for you? If it makes easier the testing i could upload a .vsix file installable from vscode. |
I'd gladly test it if you could provide a .vsix file or provide an alternative instruction. I have no experience of hacking around with VS Code like this. |
@Savelenko many thanks, you could download the vsix file here: https://github.com/haskell/vscode-haskell/releases/download/1.5.0/haskell-1.5.1-beta.vsix The command can be found in the command palette: |
Thanks, I could install it and after reloading the following error popped up immediately:
I am ready to test as many times as needed :) |
Hmm i've observed the path to the executable contains spaces |
Ok, i've uploaded a new beta version: https://github.com/haskell/vscode-haskell/releases/download/1.5.0/haskell-1.5.1-beta-2.vsix |
Yes, this solved it, thanks a lot! By the way, the spaces in |
Nice!, many thanks again |
- Add much more logging in the client side, configured with haskell.trace.client - Fix error handling of working out project ghc (See #421) - And dont use a shell to spawn the subprocess in non windows systems - Add commands Start Haskell LSP server and Stop Haskell LSP server
Having this problem again with an OpenSUSE installation. GHCup freshly installed, Extension too, on a brand new stack project. Extension Logs as following:
|
If I can provide any further data or perform any further debugging steps I'd be glad to. |
Running extension version v2.2.0 |
Can confirm all installed GHCup tools work as expected in the command line too, so no PATH issue there. Running the last frozen command manually in the same environment yields the following logs before freezing:
|
This command might install a full ghc version, can you try to run HLS on the path for your project and report the output? E.g. $ haskell-languag-server-wrapper --debug <path-to-your-sources> Note, it might take a while, if you have a stack project, it will install the necessary stack project. |
This will sound kind of unbelievable, but I can't replicate this again, since I switched distros since then. I apologize for the inconvenience 😅 |
After automatic update to 1.5.0 VS Code (OSS Code 1.55.2) shows a new status "Working out the project GHC version. This might take a while...". I've read a bit that this used to fail to appear without clear progress indication to the user but in my case it never finishes (I restarted VS Code several times and waited for ~10 minutes). Consequently, HLS never starts and there is no debug output under Haskell.
Just yesterday, before the update my whole set-up worked great, the only change is 1.5.0 of the extension. Here is my HLS environment:
The text was updated successfully, but these errors were encountered: