-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
[error] Bad RPC call to node nextls-runtime => LSP Exited => :timeout #467
Comments
i haven't actually seen that error in a prod build, only in tests
i think its a weird timing issue, will investigate further, thank you for the report! |
I'm constantly hitting this issue now. I've run next-ls locally over tcp but there are no logs or errors in its output. Is there any way I could debug this locally? |
Frequently we'd see the following error in tests, and some users were seeing in production: ``` [error] Bad RPC call to node nextls-runtime-1715431446385794000@MacBook-XXX: {:EXIT, {:badarg, [{:ets, :lookup, [:elixir_config, :parser_options], [error_info: %{cause: :id, module: :erl_stdlib_errors}]}, {:elixir_config, :get, 1, [file: ~c"src/elixir_config.erl", line: 21]}, {:elixir_compiler, :string, 3, [file: ~c"src/elixir_compiler.erl", line: 7]}, {Module.ParallelChecker, :verify, 1, [file: ~c"lib/module/parallel_checker.ex", line: 112]}, {Code, :compile_file, 1, []}]}} ``` I believe that this is caused by an internal ETS table not being booted yet, so we not await on it being present on the project node. Closes #467
I'll give it a try, thanks! |
Frequently we'd see the following error in tests, and some users were seeing in production: ``` [error] Bad RPC call to node nextls-runtime-1715431446385794000@MacBook-XXX: {:EXIT, {:badarg, [{:ets, :lookup, [:elixir_config, :parser_options], [error_info: %{cause: :id, module: :erl_stdlib_errors}]}, {:elixir_config, :get, 1, [file: ~c"src/elixir_config.erl", line: 21]}, {:elixir_compiler, :string, 3, [file: ~c"src/elixir_compiler.erl", line: 7]}, {Module.ParallelChecker, :verify, 1, [file: ~c"lib/module/parallel_checker.ex", line: 112]}, {Code, :compile_file, 1, []}]}} ``` I believe that this is caused by an internal ETS table not being booted yet, so we not await on it being present on the project node. Closes #467
Frequently we'd see the following error in tests, and some users were seeing in production: ``` [error] Bad RPC call to node nextls-runtime-1715431446385794000@MacBook -XXX: {:EXIT, {:badarg, [{:ets, :lookup, [:elixir_config, :parser_options], [error_info: %{cause: :id, module: :erl_stdlib_errors}] }, {:elixir_config, :get, 1, [file: ~c"src/elixir_config.erl", line: 21]} , {:elixir_compiler, :string, 3, [file: ~c"src/elixir_compiler.erl", line : 7]}, {Module.ParallelChecker, :verify, 1, [file: ~c"lib/module/parallel _checker.ex", line: 112]}, {Code, :compile_file, 1, []}]}} ``` I believe that this is caused by an internal ETS table not being booted yet, so we not await on it being present on the project node. Closes #467
Frequently we'd see the following error in tests, and some users were seeing in production: ``` [error] Bad RPC call to node nextls-runtime-1715431446385794000@MacBook -XXX: {:EXIT, {:badarg, [{:ets, :lookup, [:elixir_config, :parser_options], [error_info: %{cause: :id, module: :erl_stdlib_errors}] }, {:elixir_config, :get, 1, [file: ~c"src/elixir_config.erl", line: 21]} , {:elixir_compiler, :string, 3, [file: ~c"src/elixir_compiler.erl", line : 7]}, {Module.ParallelChecker, :verify, 1, [file: ~c"lib/module/parallel _checker.ex", line: 112]}, {Code, :compile_file, 1, []}]}} ``` I believe that this is caused by an internal ETS table not being booted yet, so we not await on it being present on the project node. Closes #467
Frequently we'd see the following error in tests, and some users were seeing in production: ``` [error] Bad RPC call to node nextls-runtime-1715431446385794000@MacBook -XXX: {:EXIT, {:badarg, [{:ets, :lookup, [:elixir_config, :parser_options], [error_info: %{cause: :id, module: :erl_stdlib_errors}] }, {:elixir_config, :get, 1, [file: ~c"src/elixir_config.erl", line: 21]} , {:elixir_compiler, :string, 3, [file: ~c"src/elixir_compiler.erl", line : 7]}, {Module.ParallelChecker, :verify, 1, [file: ~c"lib/module/parallel _checker.ex", line: 112]}, {Code, :compile_file, 1, []}]}} ``` I believe that this is caused by an internal ETS table not being booted yet, so we not await on it being present on the project node. Closes #467
last release got botched, re-doing it now |
should be fixed now |
This happened a few times on a different occasions but now it happens every time I restart vscode.
The relevant log lines seems to be these:
Removing
.elixir-tools
and restarting everything fixes the problem.Full log
The text was updated successfully, but these errors were encountered: