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

Issue 860180 link

Starred by 2 users
Status: Archived
Owner:
█ lushnikov@chromium.org
Last visit 28 days ago
Closed: Dec 8
Cc:
susan.boorgula@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

DevTools failed to link network resource to filesystem, mapping between Windows and Linux does not work

Reported by mulyo...@gmail.com, Jul 4 
DevTools failed to link network resource to filesystem.

Platform: Win + Linux
Chrome version: 67.0.3396.99

What are the details of your project?
- Build System: webpack
- HTTP server: node

Assets failed to link (or incorrectly linked):
on my remote linux (where node run) files are in "/main/api/lambda"
on my local Win system, (where Chrome run) they are in "c:\main\api\lambda"

so can open source code using 

"file:///c:/main/api/lambda/graphql/index.js"

but DevTools look in 

"file:///main/api/lambda/graphql/index.js"


If possible, please attach a screenshot of network sources navigator which should
show which resources failed to map

Comment 1 by krajshree@chromium.org, Jul 5

Labels: Needs-Triage-M67

Comment 2 by susan.boorgula@chromium.org, Jul 6

Cc: susan.boorgula@chromium.org
Labels: Triaged-ET
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Assigning the issue to 	lushnikov@ - owner of similar bugs  839727 ,  844221 .

lushnikov@: Request you to please have a look into the issue and help in further triaging.

Thanks..

Comment 3 by lushnikov@chromium.org, Dec 8

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