-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
Too many error messages on certain malformed code #855
Comments
Hi @dv01sw ! These errors aren't caused by your code having some error, they're caused by lexical failing entirely while handling an editor request; they're notifications from vscode itself, not from lexical. That might why you weren't able to disable them. With that said, they're indeed very distracting but this volume of failed requests is absolutely not normal. Something must be going wrong between your lexical installation and your environment. In your project you should find a Also, if you could provide some information regarding your development environment that would help a lot:
|
OS: Fedora 41 Stacktrace:
|
Or is my Elixir just too new? |
1.17.3 should be fine. You can see the complete compatibility table here. With that said I'm don't really know what's going on here. It looks like Elixir is failing to inspect a I'll transfer the issue over to the main lexical repo. The maintainers over there should be able to help better. |
Heyhey 👋
Sometimes when editing a file and introducing some syntax issue, lexical will throw up to three different error popups, and on each keypress they will animate again and also cannot be silenced. Neither by the DoNotDisturb mode, nor by clicking deactivate the notifications of this extension (because even if you deactivate the notifications of a certain extension in docker it will still show those marked as Error)
For concentrating on the code they are very distracting and don't add any value. I already know that the syntax is not correct, no need to yell at me that now also autocomplete will stop working :))
Bildschirmaufzeichnung.vom.2025-02-12.15-50-22.mp4
The text was updated successfully, but these errors were encountered: