-
Notifications
You must be signed in to change notification settings - Fork 26
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
Erlang LS server crashed #142
Comments
Hi @rlipscombe , did you already try to look at the logs or to attach to a running instance as described here? |
1 similar comment
Hi @rlipscombe , did you already try to look at the logs or to attach to a running instance as described here? |
Thanks. Not yet, no. I'll dig more into it tomorrow, once I'm back on the work laptop where this is happening. |
Hello, I'm having almost the same issue. Any hint about how to better debug it ? Here are the vscode output and erlang_ls log. I'm using the same versions as @rlipscombe. Thanks |
Have you checked rebar3 path in the settings? It seems to me that's what causes that server start failure. |
(not a duplicate of #71; that was resolved by an upgrade)
ErlangLS in VS Code is unable to talk to the server:
This is not necessarily a surprise to me, because I'm using a development build of Erlang/OTP:
...which I've awkwardly wedged into my direnv/kerl setup.
My question is this: how can I investigate this?
erlang_ls works fine with the version of Erlang as-built:
...so why isn't it working correctly when used from VS Code? What logs can I look in?
The text was updated successfully, but these errors were encountered: