question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Debugger cannot start: ERR timeout after 1000 ms: Error: timeout after 1000 ms

See original GitHub issue

Environment

Most of this can be filled out by running the VSCode command (by default bound to Ctrl+Shift+P) “ElixirLS: Copy Debug Info”

  • Elixir & Erlang versions (elixir --version): Erlang/OTP 22 [erts-10.7] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] Elixir 1.9.4 (compiled with Erlang/OTP 20)

  • VSCode ElixirLS version: 0.4.0

  • Operating System Version: win32 10.0.18363

Troubleshooting

  • [ x] Restart your editor (which will restart ElixirLS) sometimes fixes issues
  • [ x] Stop your editor, remove the entire .elixir_ls directory, then restart your editor

Crash report template

After upgrading from v0.4.0 -> v0.5.0 debugging has stopped working. The Developer’s Console states:

  ERR timeout after 1000 ms: Error: timeout after 1000 ms
    at t.RawDebugSession.handleErrorResponse (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:3160:190)
    at file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:3159:451
    at async t.RawDebugSession.shutdown (file:///C:/Program Files/Microsoft VS Code/resources/app/out/vs/workbench/workbench.desktop.main.js:3157:536)

Using git bisect I was able to track it down to this specific commit:

https://github.com/elixir-lsp/vscode-elixir-ls/commit/97066cefed8cf4111b63241ff5d931b2f3e39614

My guess is, perhaps on Windows machines, the workspace scanner times things out? The strange thing is, even on a relatively empty project (i.e. generated from mix phx.new myproj) it still does this.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
ctataryncommented, Jul 4, 2020

thanks for this! So with the change in #115 you don’t get the ERR timeout?

That’s correct. The commit before this one works, and everyone afterwards fails with the timeout.

0reactions
axelsoncommented, Jul 4, 2020

Fixed in #115

Read more comments on GitHub >

github_iconTop Results From Across the Web

An error "timeout after 1000 ms" occurs after executing stop ...
Create a PowerShell project with HttpTrigger function. Debug it and then stop debugging when hitting to an unset breakpoint. Check the result.
Read more >
Cannot connect to runtime process, timeout after 10000 ms
This is due to VS debug option: debug JavaScript turned on, but the browser in question is not allowing debugger to connect to...
Read more >
Cannot debug in visual studio 2017 - Stack Overflow
I'm using it successfully with the following options enabled. In Visual Studio go to: Tools -> Options -> Debugging -> General.
Read more >
Error: Timeout While Debugging Web Services - Microsoft Learn
When you are stepping into an XML Web service from calling code, the call may sometimes time out, with the result being that...
Read more >
Async Methods - Testing Library
The default timeout is 1000ms . The default onTimeout takes the error and appends the container 's printed state to the error message...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found