New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 778493 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Last visit 28 days ago
Closed: Dec 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Automatic source mapping does not work with node --inspect

Reported by gti...@wikimedia.org, Oct 26 2017

Issue description

DevTools failed to link network resource to filesystem.

Platform: Linux (Ubuntu 16.04.3)
Chrome version: 61.0.3163.100

What are the details of your project?
- Source code (if any): https://github.com/wikimedia/restbase/
- Build System: -
- HTTP server: node
I have enabled the experimental feature Persistence 2.0.

Assets failed to link (or incorrectly linked):
Running node on a vagrant box with --inspect. The files are in an NFS shared folder accessible to both guest and host. With manual mapping (file:///path/on/guest -> file:///path/on/host) this worked well; with automatic mapping it doesn't and there does not seem to be any way to disable it.

If possible, please attach a screenshot of network sources navigator which should show which resources failed to map
All of them. There is a separate Filesystem and Network tab; Chrome does not recognize that they contain the same files. I'm debugging something that requires server restart between debug runs; this makes DevTools impossible to use as the network tab is emptied on each server restart, and files are only added as they are encountered by node, so there is no way to set breakpoints (and they do not persist automatically).
 
Cc: sc00335...@techmahindra.com lushnikov@chromium.org
Labels: Needs-Triage-M61 Triaged-ET OS-Linux
cc'ing lushniko@ from   Issue 777337  for help in further triaging of this.

Thanks!

Comment 2 by ajha@chromium.org, Oct 31 2017

Cc: -lushnikov@chromium.org
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Can you please check if it works for you on latest chrome canary? I use node debugging + persistence pretty often it always worked for me.
Status: Archived (was: Assigned)
Workspaces 2.0 is imperfect and there's no feasible way to make it work for everybody. Archiving since we currently don't have resources to allocate towards improving Workspaces story.


Sign in to add a comment