Closed mitchellwrosen closed 4 months ago
I noticed this for the cabal codebase as well. I think it is a symptom of lacking multiple home unit support which requires cabal 3.12 and HLS head to work properly.
Is this reproducible with the latest HLS and cabal?
Yes, it is, and I have a slightly more detailed repro this time around:
cabal build
at the command-line just for good measurecabal-install/src/Distribution/Client/Main.hs
and let hls settle ("setting up" followed by "indexing")Cabal/src/Distribution/Simple/Command.hs
That's exactly the kind of issues that should be fixed by multi-repl: True
, once cabal-3.12 is released.
Ill try to use it.
Works with the pre-release and HLS 2.8.0.0:
Note the hover on the right.
Okay, tentatively closing, then.
Hello all, apologies for the low-quality bug report, but I wasn't able to find anything like this in the issue tracker.
Put simply, HLS simply tends to stop working, especially on bigger projects (but why does that matter?)
For example, I'm currently poking around the
cabal
codebase for the first time. You can follow along by:cabal build cabal-install
)cabal-install/src/Distribution/Client/Main.hs
I also have
ghcid
running in another terminal withghcid -c 'cabal repl cabal-install'
, which seems to always report accurate information. That's the easiest way to tell when HLS is wrong - at some point it stops agreeing withghcid
, and it's always wrong when it does.In a third terminal I have the LSP logs visible at
TRACE
level. I can see that (when HLS becomes broken) it still seems to be handling many requests. Here's an ugly dump:But within the editor, I'm no longer getting any feedback whatsoever. I just have to restart HLS, and then it works again.
Again, apologies for the relatively low-quality bug report. I just wanted to make sure that this issue is known. I'd be happy to jump on a call to assist in collecting more information, if that would be helpful. It's easy for me to trigger this behavior on my end. Thanks!