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

Issue 804680 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 796251
Owner:
Last visit 28 days ago
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Mapping are inferred automatically

Reported by tuh...@gmail.com, Jan 23 2018

Issue description

DevTools failed to link network resource to filesystem.

Platform: Windows
Chrome version: 63.0.3239.132

What are the details of your project?
- Source code (if any): local
- Build System: gulp
- HTTP server: local

Assets failed to link (or incorrectly linked):
1. chrome:flag => 'dev tool use' checked
2. sourcemap don't read

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

 

Comment 1 by l...@chromium.org, Jan 23 2018

Labels: Needs-Feedback
Owner: lushnikov@chromium.org
Thanks for the report.  We need some more information to reproduce the error you are seeing.  Do you happen to have an open source version?
Labels: Needs-Triage-M63

Comment 3 by tuh...@gmail.com, Jan 31 2018

gulp version is 3.9.1
but another resource is success
Project Member

Comment 4 by sheriffbot@chromium.org, Jan 31 2018

Cc: l...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "luoe@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

Comment 5 by l...@chromium.org, Jan 31 2018

Mergedinto: 796251
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment