-
-
Notifications
You must be signed in to change notification settings - Fork 33.2k
Closed
Labels
coverageIssues and PRs related to native coverage support.Issues and PRs related to native coverage support.inspectorIssues and PRs related to the V8 inspector protocolIssues and PRs related to the V8 inspector protocol
Description
Version
v19.3.0
Platform
Darwin MacBook-Pro-2.guest.corp.microsoft.com 22.2.0 Darwin Kernel Version 22.2.0: Fri Nov 11 02:08:47 PST 2022; root:xnu-8792.61.2~4/RELEASE_X86_64 x86_64
Subsystem
inspector
What steps will reproduce the bug?
$ NODE_V8_COVERAGE=/tmp node -p "inspector.url()"
undefined
$ NODE_V8_COVERAGE=/tmp node -p "inspector.open()"
node:inspector:172
throw new ERR_INSPECTOR_ALREADY_ACTIVATED();
How often does it reproduce? Is there a required condition?
100%
What is the expected behavior?
I would expect, regardless of whether NODE_V8_COVERAGE
is set, to be able to inspector.open()
if there is no inspector.url()
, and then after calling that be able to access inspector.url()
What do you see instead?
If NODE_V8_COVERAGE is set, inspector.url()
is undefined but inspector.open()
throws an error.
Additional information
Originally reported on microsoft/vscode-js-debug#1507
It looks like new inspector.Session().connect()
does still work in case, so we could 'fake' the inspect server as a workaround, but this is a complex hack.
Metadata
Metadata
Assignees
Labels
coverageIssues and PRs related to native coverage support.Issues and PRs related to native coverage support.inspectorIssues and PRs related to the V8 inspector protocolIssues and PRs related to the V8 inspector protocol