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

Issue 667502 link

Starred by 1 user
Status: Fixed
Owner:
pfeldman@chromium.org
Closed: Sep 2017
Cc:
█ nednguyen@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

DevTools: remove /browser remote debugging endpoint from desktop.

Project Member Reported by pfeldman@chromium.org, Nov 21 2016 
It'll be accessible via browser/<guid>.

I have a patch pending, but it fails with telemetry. 

Ned, over to you for advice. How do I detect that I'm running as a  telemetry driver? I could leave it surfacing at browser/ for the tests. Any unique flags passed to all chromes under telemetry?

Comment 1 by nedngu...@google.com, Nov 21 2016

Cc: nednguyen@chromium.org
Owner: eyaich@chromium.org

Comment 2 by pfeldman@chromium.org, Nov 30 2016

Owner: nednguyen@chromium.org
ping

Comment 3 by nedngu...@google.com, Nov 30 2016

Owner: pfeldman@chromium.org
Pavel: I think the best way is fixing telemetry so that it can adopt to your change? Can you explain to me how is telemetry failing?

Comment 4 by pfeldman@chromium.org, Nov 30 2016

Owner: nednguyen@chromium.org
Ah! You are missing my patch with the test failures. The patch linked to this bug, but not the other way around, sorry!

https://codereview.chromium.org/2514933003/

I am actually wondering myself why it fails.

Comment 5 by dgozman@chromium.org, Sep 21 2017

Owner: pfeldman@chromium.org
Status: Fixed (was: Assigned)
I think this has been fixed recently.
►

Sign in to add a comment