-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
node inspect restart prints Debugging/For-help message twice #39272
Labels
debugger
Issues and PRs related to the debugger subsystem.
Comments
Trott
added a commit
to Trott/io.js
that referenced
this issue
Jul 5, 2021
Running "restart" in the debugger confusingly prints an out-of-date "Debugger listening on..." message before printing a second updated one. Refs: nodejs#39272
Trott
added a commit
to Trott/io.js
that referenced
this issue
Jul 5, 2021
Running "restart" in the debugger confusingly prints an out-of-date "Debugger listening on..." message before printing a second updated one. Refs: nodejs#39272
Trott
added a commit
to Trott/io.js
that referenced
this issue
Jul 6, 2021
Running "restart" in the debugger confusingly prints an out-of-date "Debugger listening on..." message before printing a second updated one. Refs: nodejs#39272
Trott
added a commit
to Trott/io.js
that referenced
this issue
Jul 6, 2021
Running "restart" in the debugger confusingly prints an out-of-date "Debugger listening on..." message before printing a second updated one. Refs: nodejs#39272
Trott
added a commit
to Trott/io.js
that referenced
this issue
Jul 7, 2021
Running "restart" in the debugger confusingly prints an out-of-date "Debugger listening on..." message before printing a second updated one. Refs: nodejs#39272
Trott
added a commit
to Trott/io.js
that referenced
this issue
Jul 7, 2021
Running "restart" in the debugger confusingly prints an out-of-date "Debugger listening on..." message before printing a second updated one. Refs: nodejs#39272
Trott
added a commit
to Trott/io.js
that referenced
this issue
Jul 8, 2021
Running "restart" in the debugger confusingly prints an out-of-date "Debugger listening on..." message before printing a second updated one. Refs: nodejs#39272 PR-URL: nodejs#39273 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Trott
added a commit
to Trott/io.js
that referenced
this issue
Jul 10, 2021
Trott
added a commit
to Trott/io.js
that referenced
this issue
Jul 11, 2021
Currently, we say "listening" when we are ending the server. Change it to "ending". Fixes: nodejs#39272
Trott
added a commit
to Trott/io.js
that referenced
this issue
Jul 12, 2021
Currently, we say "listening" when we are ending the server. Change it to "ending". Fixes: nodejs#39272
Trott
added a commit
to Trott/io.js
that referenced
this issue
Jul 12, 2021
Currently, we say "listening" when we are ending the server. Change it to "ending". Fixes: nodejs#39272
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Every time.
What is the expected behavior?
After issuing
restart
in the debugger CLI, it will only print "Debugger listening on...For help..." message once.What do you see instead?
It repeats the initial message from the start of the session, then issues the correct second message.
Additional information
The text was updated successfully, but these errors were encountered: