michaelpj
commented
2 years ago I'm going to be annoying and not help with the object-level problem (no idea, sorry!) but just list a number of issue-reporting problems that Richard's helpful stream-of-consciousness report made me notice:
- The issue template should link to the Troubleshooting doc page and ask people to read it before opening an issue.
- The Troubleshooting doc page doesn't list the "HLS compiled with the wrong version of GHC" issue, although I suspect it's a common one.
- The issue template should tell users of the vscode extension to consult the docs for the extension to find out where their binaries are installed to. If the extension docs don't say where to find them, we should add that.
- The issue template should link to how to get client logs. This could go via the Troubleshooting section on troubleshooting the client (which does tell you how to get the vscode logs!).
- Do setup issues like mismatched GHC versions get reported well in all the clients we know of, especially vscode? Can we improve it if not?
- The troubleshooting section in the vscode extension docs could be extended a lot, and should probably also link to the HLS troubleshooting page.
jneira
goldfirere
wz1000
fendor
Anton-Latukha
pepeiborra
Your environment
Output of
haskell-language-server --probe-toolsorhaskell-language-server-wrapper --probe-tools: I don't know. Neither of these executables is on my PATH, and I don't know where they are. HLS was installed by VS Code. I'm pretty sure I saw a notification recently that HLS was being upgraded to 1.5.0. Happy to give you more information if told how to retrieve the information.Which OS do you use: MacOS Which lsp-client do you use: VS Code Describe your project (alternative: link to the project): GHC
Steps to reproduce
Open an editor to a GHC source file, and see that nothing from HLS works.
Expected behaviour
HLS should do stuff, like allow me to jump to a definition, or give me the type of something by pointing at it.
Actual behaviour
Nothing. It's like HLS is off. When I looked at the Problems pane, I briefly saw a message saying (I think) that ghcide was compiled against GHC 8.10.7 while GHC 8.10.5 is the one installed. I can't tell you the error message exactly because it disappeared while I was looking at it. I don't know how to get it back. I have nothing called
ghcidein my PATH.Include debug information
Execute in the root of your project the command
haskell-language-server --debug .and paste the logs here: I don't havehaskell-language-serverin my PATH, and I don't know where it is, so I can't do this. :(Paste the logs from the lsp-client, e.g. for VS Code: I don't know how to do this. That link did not contain any instructions for how to produce logs for lsp-client.
Other background info
In other work, I did change the GHC in my path several times today, including GHC 8.10.7 for a little while. With GHC 8.10.7, I installed the newest cabal-install. (I would have used GHC 8.10.5, my main version of GHC these days, but I was caught by https://github.com/haskell/network/issues/518, which required using a higher GHC.) But I did nothing with anything called ghcide.
HLS appears to work on non-GHC projects. The GHC tree I'm working in was built bootstrapping from GHC 8.10.5.
I suppose I could just upgrade to GHC 8.10.7. But I have a bunch of trees bootstrapped from GHC 8.10.5, and so doing this would require quite a bit of rebuilding.
Any advice about how to get myself unstuck -- or, even better, how I can learn more about what's going on -- is appreciated. Thanks!