-
-
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
Indexing getting stuck #854
Comments
This is interesting:
This is likely what's killing indexing on your computer. Can we dig in there? |
I wouldn't know how tbh, the call to that is coming from lexical if I understand correctly? |
This might be tedious, but on one of these files, Line 72 has something with
|
Though, now that I see this, is lexical being run in a monorepo? I'm not sure how well that'd work. |
It is, yeah – as in: the Elixir project is not at the root of my repo, but it is the only Elixir project in the repo. |
That would be this one: |
Yeah, i see why that doesn't work, but it shouldn't crash things. |
Thanks for the hint, I've been opening the Elixir project separately while working on it and I have not encountered the issue anymore, so that does seem to be the cause, that's good enough for me. I kind of expected the |
I quite frequently run into a situation where lexical gets stuck indexing indefinitely, and sometimes it appears to spin up several indexing tasks which all end up stuck / don't leave the vscode notification center, this is a bit distracting:
Unfortunately reloading the editor does not help at all, once this starts happening, lexical always shows an indexing notification that never goes away when it starts, and the only thing that helps is deleting the indexes directory under
.lexical
and then restarting the editor.After that, the indexing then completes immediately in around a second and everything works normally again.
It just happened to me again and I noticed the last line in the
.lexical/project.log
is this:In the
lexical.log
there is this:Is there any way to avoid this?
The text was updated successfully, but these errors were encountered: