Issue metadata
Sign in to add a comment
|
DevTools: dedicated Node.js frontend does not work |
||||||||||||||||||||||
Issue descriptionChrome Version: 72.0.3614.0 OS: MacOS What steps will reproduce the problem? (1) go to chrome://inspect and open dedicated DevTools frontend for Node.js (2) run node --inspect from terminal What is the expected result? DevTools attach to Node.js target and allow to debug/inspect it. What happens instead? DevTools detect Node.js target, send a bunch of protocol commands but never receive an ack. I suspect https://chromium-review.googlesource.com/c/chromium/src/+/1321854 but did not bisect this one.
,
Nov 27
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ec9cbf0f5445d081f7bd2c9b3c1e596e6921dc16 commit ec9cbf0f5445d081f7bd2c9b3c1e596e6921dc16 Author: Dmitry Gozman <dgozman@chromium.org> Date: Tue Nov 27 18:13:56 2018 [DevTools] Make ForwardingAgentHost work with flatten protocol Bug: 906483 Change-Id: I3da2cd45f2ab6e2d88e42c97f0de48208f210ad6 Reviewed-on: https://chromium-review.googlesource.com/c/1350966 Reviewed-by: Pavel Feldman <pfeldman@chromium.org> Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#611195} [modify] https://crrev.com/ec9cbf0f5445d081f7bd2c9b3c1e596e6921dc16/content/browser/devtools/devtools_session.cc [modify] https://crrev.com/ec9cbf0f5445d081f7bd2c9b3c1e596e6921dc16/content/browser/devtools/devtools_session.h [modify] https://crrev.com/ec9cbf0f5445d081f7bd2c9b3c1e596e6921dc16/content/browser/devtools/forwarding_agent_host.cc [modify] https://crrev.com/ec9cbf0f5445d081f7bd2c9b3c1e596e6921dc16/content/browser/devtools/forwarding_agent_host.h [modify] https://crrev.com/ec9cbf0f5445d081f7bd2c9b3c1e596e6921dc16/third_party/blink/renderer/devtools/front_end/node_main/NodeMain.js
,
Nov 27
,
Nov 28
Tried testing this issue on Mac OS 10.14.1 on the reported version 72.0.3614.0 and the latest M-72 72.0.3624.0 by following the below steps. 1. Launched Chrome and navigated to chrome://inspect. 2. Clicked on 'Open dedicated DevTools for Node'. 3. From terminal ran 'node --inspect' and could see message like 'Debugger listening on ws://127.0.0.1:9229/4b22420e-2732-4e15-9d62-331c9d178253 For help see https://nodejs.org/en/docs/inspector' on terminal. The same behavior is observed on the reported version. Attached is the screen cast for reference. dgozman@ Request you to check and confirm if anything is missed from our end in verifying the issue and help us to verify the fix on the latest M-72 build. Thanks... |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dgozman@chromium.org
, Nov 20Owner: alph@chromium.org