Dorgan
Dorgan
I'm not sure this is the right approach for this issue, we need to support workspace folders/multiple root projects(like expert) that might be running on different elixir/erlang versions This approach...
Sorry, I misread part of your PR and I'm wrong about this locking expert to a single version pair. You're right on most of it, and the only scenarios where...
tl;dr I think we can use this to mitigate the issue temporarily but we still need to fix the root cause
> I would suggest copying to the project _build directly so that all built assets can be easily cleaned instead of having dangling built assets hanging around, even after their...
@john-eevee for what it's worth, Expert does not depend on version managers, it will use whichever `elixir` you have in your `PATH`(see [here](https://github.com/elixir-lang/expert/blob/main/apps/expert/lib/expert/port.ex#L41)). But if you use a version manager,...
@john-eevee > If I'm not mistaken the original issue was due to the Erlang version mismatch? That's part of the issue, the real problem is that we're not getting the...
@heywhy that's great to hear, thank you for your time working on this PR! 🙇
Done in #205
The indexes are stored in the `.expert/indexes` folder, are you able to verify if these folder/files aren't being created? Also, can you check your logs/your editor logs to see if...
@salfum can you provide the logs in `.expert/project.log`? The error you're seeing is benign(as in, it's not what's causing the crash) so I presume the project node is crashing and...