-
-
Notifications
You must be signed in to change notification settings - Fork 391
Unexpected exception on notification, please report! #143
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
Comments
Oh dear! Sadly, our error message is pretty crap, and doesn't tell us which global is missing, which would be by far the most useful piece of information. I've sent a patch to improve that: haskell/ghcide#598 Does this reproduce reliably? Or is it a one-off after a sequence of edits that you can't reproduce? |
I see "Client does not support watched files. Falling back to OS polling" in the logs, and use of Atom. My guess is most testing is done on clients which do support watched files, so that's seems like a possible lead. |
That's a good lead indeed. Even more, there's a few
So the problem is obvious: the client is very buggy. It is sending The We can patch this on our side by registering the global unconditionally, but @aryairani you should probably switch to another plugin/editor combination |
I have moved the issue to the ghcide tracker where it belongs, thanks for the report @aryairani |
hie/ghcide/haskell-language-server noob here, so I apologize for a possibly-low-quality bug report.
I get a bunch of
Exception: user error (Pattern match failure in do expression at src/Development/IDE/Core/Shake.hs:157:5-10)
(given in the code block below) when I open my Haskell files. Not sure if this is actually related to the "Unexpected exception on notification" message in the issue title, which I also see in the log, but I don't know that it isn't :)The full log is here: https://gist.github.com/aryairani/90410cce8d5c132b9290329f4d326647
I am using the Atom
ide-haskell-hie
plugin v0.12.0 with the custom hie-wrapper set tohaskell-language-server-wrapper
.Keep up the good work!
The text was updated successfully, but these errors were encountered: