Closed ken-kost closed 4 months ago
Is it the right place to report? Probably ash support channels are better in this case. Do you have a small repo that reproduces it?
I don't but it should be easy to reproduce. Okay, I'll close the issue then, thanks for the feeback.
To be clear, I'm pretty positive this has nothing to do with Ash at all. Deleting the .elixir_ls
directory tends to fix this kind of issue, and it can happen on any dependency change.
yep, my bad
Oh, no worries I wasn't calling you out, I just think the issue should potentially still remain open, as there is a situation where elixir-ls seems to get into a state where it can't operate after dependencies change.
It's notoriously hard to reset mix and app controller state without restarting the os process. AFAIK it affects all elixir language servers to some extent. Do you happen to have a reliable repro? I fixed a few similar issues in the last years
I don't have a reproduction unfortunately 😢 I think it is both transient and timing related. The only things I've noticed so far is that it seems to happen more with bigger dependencies/bigger upgrades, and it doesn't always happen.
Yep, switching branches in bigger projects with > 20 deps triggers various bugs in mix and hex. Just today I was able to trigger corrupted hex cache from the command line only
Environment
Current behavior
After I updated ash dep from 3.0 to 3.1 I got error in mix: