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

Issue 796886 link

Starred by 4 users

Issue metadata

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



Sign in to add a comment

DevTools failed to link network resource to filesystem.

Reported by steven.p...@gmail.com, Dec 21 2017

Issue description

DevTools failed to link network resource to filesystem.

Platform: <Linux/Win/Mac>
Chrome version: 63.0.3239.84 - 65.0.3299.5

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

Assets failed to link (or incorrectly linked):
Everything
http://take.ms/jtHjw
http://take.ms/KvW16

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

Is it possible to rollback the ability to Map files manually?
It was working without a hiccup in past, I don't mind to select files manually
 
Golden Planet ApS - Google Chrome 2017-12-21 14.18.56.png
43.2 KB View Download
Cc: lushnikov@chromium.org vamshi.k...@techmahindra.com
Labels: Needs-Triage-M63 Triaged-ET
Mergedinto: 794946
Status: Duplicate (was: Unconfirmed)
This issue seems to be similar to that of https://bugs.chromium.org/p/chromium/issues/detail?id=794946, Hence, CC'ing  lushnikov@chromium.org and duplicating into  issue#794946 .

Note: Please feel free to undupe or revert if both are not same.

Thanks!
Labels: DevTools-Workspaces
Owner: lushnikov@chromium.org
Status: Assigned (was: Duplicate)
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