-
-
Notifications
You must be signed in to change notification settings - Fork 371
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
HLS 1.5 appears to not handle hs-boot files correctly #2365
Comments
Many thanks for reporting the bug quickly, @mpickering just has reported it in irc. |
Yes, in the case I reported it seems related to the |
Ok, there are at least two tests in ghcide about hs-boot files haskell-language-server/ghcide/test/exe/Main.hs Lines 437 to 481 in a03013c
But they did not catch the bug, maybe cause they dont reproduce the bug context Will try to reproduce with ghcup-hs, it is a relatively small project and contains at least one hs-boot file |
This issue was introduced by ab46fe8 , which changed the logic to compute the GHC session with dependencies for a file. The |
Thanks for the diagnosis @wz1000, I think you are 100% correct. Bummer! Is anyone able to contribute a test case and a fix? If not, I'll take a look this weekend or next week. |
The ci workflow of the release commit for ghc-9.0.1 executed tests succesfully:
Tests dont check the absence of error diagnostics explicitly, so maybe that is the cause they did not catch the bug |
With HLS 1.5 (using GHC 9.0.1), using the VS Code extension on Windows 10, I'm getting errors when running HLS on the GHC codebase. These errors seem to be caused by a problem loading an
hi-boot
interface file.Running HLS on GHC commit f8c1c549bbb02cb0a943a9ae49dee922c96d85c4, I'm getting the following errors:
Show/hide interface file errors
These all seem to do with failing to load the
hi-boot
file forGHC.Unit.Types
.I have cleared the ghcide cache as well as the
_hie_bios
folder, and the error persists. Switching back to HLS 1.4 immediately fixes the problem.The text was updated successfully, but these errors were encountered: