-
-
Notifications
You must be signed in to change notification settings - Fork 390
Non fatal error "Data.HashMap.Base.(!): key not found" #181
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
I was browsing the output of the extension (for another issue) and saw that I can reliably trigger this by saving the document I have open. I managed to recreate this with a clean install of VS Code and the latest version of the extension with default settings (so it downloaded and used the latest HLS binaries). Specifically, creating a project with stack new mwe simple --resolver lts and opening
It looks like the first one is caused by opening file, and I saw each of the ones at the end happen as soon as I saved the file (this was without making any changes to the file, though I saw the same error logged if I made changes to the file and saved it). Does this match what you've seen? |
Yeah, i had not recognize the pattern but it matches your observations |
I was starting to play around with HLS today and decided to take a look at this issue because it annoys me a lot whenever I startup HLS to see this 😄 The problem happens even on a brand new Stack project ( Though I can't tell (yet?) the root cause, I have found some interesting things, by comparing with running Ghcide directly on the same project (which doesn't throw). As showed by the exception, the problem happens in This "empty" As I have no effing clue what this is or what this is supposed to return, I can hardly go further in this investigation 😄 But notice that Ghcide does not go through this function when started directly 🤷♂️ Hope this newbie investigation can help someone more knowledgeable understand what's going on! |
cc @wz1000 |
This is harmless, I would suggest you ignore it for now. It happens because we cannot initially construct a complete module graph since we don't know about all the files in the project. This is soon resolved, so it disappears. |
I got this while trying to evaluate some code inline like: data Person = Person { name :: String, age :: Int} deriving Show -- deriving (Show, Generic)
-- >>> Person "codygman" 0 I did evaluate the part with deriving generic first so not sure if that's related here. All I know is the only error that came up:
Actually something else to note that is every time I click "Evaluate" it always tries to rebuild, so I think this could be a case where not having that module information is a cause. |
I'm getting a similar error trying to module Main where
data Boolean = O | I
-- >>> not O
not :: Boolean -> Boolean
not O = I
not I = I
(VSCode on mac) |
The text was updated successfully, but these errors were encountered: