-
Notifications
You must be signed in to change notification settings - Fork 196
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
Can't continue due to errors on dependencies error: tell the client #1025
Comments
I am getting this error with
It be nice to know what is causing to fail? |
Anything. The error comes from mix and it's not very descriptive. Do you have a repo that reproduces it reliably? |
Yes, it is private sadly... I am beginning to wonder if it is Oban Pro+Web as they run in a separate repo and require auth. |
I'm seeing the same error. We also use Oban Pro... going to look into that as the source of the problem. |
Not sure the cause for us but deleting |
Environment
Current behavior
When I change branch in my elixir project, elixirls fails to start and requires me to call
mix deps.get
. I consider this normal. The dependencies are quite different between the branches. I just runmix deps.get
and that fixes the issue.However, I do not get any warning in my editor that the LSP is disabled due to that issue.
If I ask my editor to show me the LSP log file, then I can see the message:
However this is not very handy, I would like to be proactively warned that I should take this step of refetching the dependencies.
Expected behavior
I believe a clean solution would be for elixirls to "catch this error", tell the client, and then "rethrow it" -- sorry about the terminology, I'm pretty sure that's not proper elixir talk... And my understanding is that this is possible through the LSP protocol, and elixirls already does that in one place:
It would be great if such an "error" (instead of warning in the example I pasted) message was sent if the dependencies are not up-to-date and elixirls cannot operate.
The text was updated successfully, but these errors were encountered: