Closed urielfcampos closed 1 month ago
When you shut down your editor, are there any elixir processes running? If there are, kill them and start your editor.
I've confirmed there are no elixir processes running after shutting down the editor and the error persists after starting the editor.
Can you paste in the entire stack trace? It is available in .lexical/*.log
in your project's root directory.
Do you have an exceptionally large project? Like something over 500k lines? The project needs to build and be indexed before you can use go-to-definition, you should see progress messages in your editor to indicate when it's available. It looks like we need better error handling somewhere.
Yup, the project i'm working on has over a million lines 😅 I will get the log soon. May i send it over to you privately ?
edit or if you have an obfuscation tool that i could use, it would be lovely too
you can send it privately via a DM on our discord.
Hey everyone !
Since the latest release, i started getting this error on my lexical extension on VSCode when i try to use
go to definition
for a module. Any ideas on how to fix it ?Here's some information on my system: Lexical startup.
erlang 26.2.5 elixir 1.16.2-otp-26
the error snippet from the output
Thanks in advance 🙇🏻