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

Issue 708869 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Last visit 29 days ago
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

workspaces not populating local folder

Reported by ahouseho...@justfab.com, Apr 6 2017

Issue description

DevTools failed to link network resource to filesystem.

Platform: Mac
Chrome version: Version 59.0.3063.0 (Official Build) canary (64-bit)

Get help with Chrome

Report an issue



What are the details of your project?
- Source code (if any): http://github.com/example/example
- Build System: gulp/grunt/webpack/rollup/...
- HTTP server: node HTTP/nginx/apache...

Assets failed to link (or incorrectly linked):
1. the option to map to a file system resource is no longer prsenting
2.
3.

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

 

Comment 1 by ajha@chromium.org, Apr 6 2017

Cc: einbinder@chromium.org
Labels: OS-Mac
Cc'ing 	einbinder@ for help in better triaging of this. Could  Issue 707219  be related as well.
Labels: Needs-Feedback
Cc: -einbinder@chromium.org
Owner: lushnikov@chromium.org
Right, there's no more option to map file system resources. Instead, we're inferring mappings automatically for you.

Doesn't it map for you?
It was not initially but seems to have sorted itself out now. Feel free to close!
Project Member

Comment 6 by sheriffbot@chromium.org, Apr 6 2017

Cc: ranjitkan@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: Fixed (was: Unconfirmed)
Niceee!

Sign in to add a comment