Uh oh!
There was an error while loading. Please reload this page.
inspector: throw error when activating an already active inspector - #33015
Closed
joyeecheung wants to merge 2 commits into
Closed
inspector: throw error when activating an already active inspector#33015joyeecheung wants to merge 2 commits into
joyeecheung wants to merge 2 commits into
Conversation
When the user tries to activate the inspector that is already active on a different port and host, we previously just silently reset the port and host stored in the Environment without actually doing anything for that to be effective. After this patch, we throw an error telling the user to close the active inspector before invoking `inspector.open()` again.
joyeecheungforce-pushed
the
inspector-open
branch
from
April 23, 2020 05:32
98fa7bf to
2912300CompareZYSzys
approved these changes
Apr 23, 2020
eugeneo
approved these changes
Apr 23, 2020
devsnek
approved these changes
Apr 23, 2020
cjihrig
approved these changes
Apr 23, 2020
Uh oh!
There was an error while loading. Please reload this page.
nodejs-github-bot
commented
Apr 27, 2020
Collaborator
nodejs-github-bot
commented
Apr 28, 2020
Collaborator
nodejs-github-bot
commented
Apr 30, 2020
Collaborator
nodejs-github-bot
commented
Apr 30, 2020
Collaborator
nodejs-github-bot
commented
May 8, 2020
Collaborator
nodejs-github-bot
commented
May 19, 2020
Collaborator
nodejs-github-bot
commented
May 19, 2020
Collaborator
BridgeAR
approved these changes
May 23, 2020
Collaborator
BridgeAR pushed a commit
to BridgeAR/node
that referenced
this pull request
May 24, 2020
When the user tries to activate the inspector that is already active on a different port and host, we previously just silently reset the port and host stored in the Environment without actually doing anything for that to be effective. After this patch, we throw an error telling the user to close the active inspector before invoking `inspector.open()` again. PR-URL: nodejs#33015Fixes: nodejs#33012 Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com> Reviewed-By: Eugene Ostroukhov <eostroukhov@google.com> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
BridgeAR
commented
May 24, 2020
Member
Landed in dd5f209 🎉 |
codebytere pushed a commit
that referenced
this pull request
Jun 18, 2020
When the user tries to activate the inspector that is already active on a different port and host, we previously just silently reset the port and host stored in the Environment without actually doing anything for that to be effective. After this patch, we throw an error telling the user to close the active inspector before invoking `inspector.open()` again. PR-URL: #33015Fixes: #33012 Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com> Reviewed-By: Eugene Ostroukhov <eostroukhov@google.com> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Merged
codebytere pushed a commit
that referenced
this pull request
Jun 30, 2020
When the user tries to activate the inspector that is already active on a different port and host, we previously just silently reset the port and host stored in the Environment without actually doing anything for that to be effective. After this patch, we throw an error telling the user to close the active inspector before invoking `inspector.open()` again. PR-URL: #33015Fixes: #33012 Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com> Reviewed-By: Eugene Ostroukhov <eostroukhov@google.com> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
codebytere pushed a commit
that referenced
this pull request
Jul 8, 2020
When the user tries to activate the inspector that is already active on a different port and host, we previously just silently reset the port and host stored in the Environment without actually doing anything for that to be effective. After this patch, we throw an error telling the user to close the active inspector before invoking `inspector.open()` again. PR-URL: #33015Fixes: #33012 Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com> Reviewed-By: Eugene Ostroukhov <eostroukhov@google.com> Reviewed-By: Gus Caplan <me@gus.host> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Merged
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the user tries to activate the inspector that is already active
on a different port and host, we previously just silently reset
the port and host stored in the Environment without actually doing
anything for that to be effective. After this patch, we throw
an error telling the user to close the active inspector before invoking
inspector.open()again.Fixes: #33012
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes