-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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 processing "setBreakpoints" on console using new inspector protocol, but breakpoint works #21731
Comments
Which version of Node are you using? Probably 7.5 or .6 in which case this is nodejs/node#11589 |
You are right, node v7.7.0 |
Ok. This is a nasty bug. But you'll see the same thing using chrome devtools, and there's not a lot I can do. |
I should add a note to docs somewhere... |
ok, thank you. |
I'll leave it open so I remember to make a note somewhere :) |
What a powerful todo list ;) |
I made a change to make this a slightly better experience. And I wrote a SO question for people to find: http://stackoverflow.com/questions/42567417/error-set-breakpoints-request-timed-out-while-debugging-node-in-vs-code/42567422#42567422 It seems too specific to add to official docs, but I did want to write it down somewhere. |
Steps to Reproduce:
I have a project with node in typescript with sourcemaps.
Using this configuration:
With the new inspector protocol I have an error on console when I set or remove a breakpoint when debugging, but the breakpoint works.
Console output when I set or remove a breakpoint:
Error processing "setBreakpoints": Error: Set breakpoints request timed out at Timeout.setTimeout (c:\Program Files (x86)\Microsoft VS Code\resources\app\extensions\ms-vscode.node-debug2\node_modules\vscode-chrome-debug-core\out\src\utils.js:55:24) at tryOnTimeout (timers.js:232:11) at Timer.listOnTimeout (timers.js:202:5) Thu, 02 Mar 2017 09:04:15 GMT express deprecated req.host: Use req.hostname instead at <anonymous>:1:49
The text was updated successfully, but these errors were encountered: