New issue
Advanced search Search tips

Issue 741793 link

Starred by 3 users
Status: WontFix
Owner: ----
Closed: Jul 2017
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

bug 675411 has been miscategorised

Reported by luke.lei...@gmail.com, Jul 12 2017 
UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36

Steps to reproduce the problem:
https://bugs.chromium.org/p/chromium/issues/detail?id=675411 has been miscategorised by user a....@chromium.org.  i would email them but i do not expect there to exist a user named "a....@chromium.org".

What is the expected behavior?

What went wrong?
"a......@chromium.org" misread the report (did not read it in full), saw the word "VPN" and went "oh this must be solely and exclusively related to a VPN".

i've made several comments that this bug has been miscategorised... but the comments have been ignored.

with there being no way (unlike with bugzilla) for the reporter of a bug to add or change categorisation, the only way left to escalate this to the attention of the developers is.... to raise a bugreport... about the bugreport.

the reason why i am trying to bring your attention to this issue is because google announced recently that they are trying to help poorer countries by improving the responsiveness of the web browsing experience.  675411 outlines a critical recommendation to add a test case to the chromium test suite (userspace network filtering/throttling) which would allow developers to *reliably* see what using chromium is *really* like under network conditions in the very countries that they've been asked to help.

Did this work before? N/A 

Chrome version: 56.0.2924.76  Channel: n/a
OS Version: 
Flash Version:

Comment 1 by ajha@chromium.org, Jul 13 2017

Status: WontFix (was: Unconfirmed)
Thanks  luke.leighton@ for raising this. The ignored comments by TE team was probably rooted to added 'TE-NeedsTriageHelp' component to that bug, which means that Testing team is unable to test the scenario and would require the respective team's help to triage this further(in  Issue 675411  case, Network team)

Apologies for the hassle, I would change the category of  Issue 675411  to more generic(Internals>Network) category and request the Network team to take a look into this.

Closing this as acknowledgement for  Issue 675411  and changing the bug category accordingly.

Comment 2 by luke.lei...@gmail.com, Jul 13 2017 

no problem, sorry for raising a bugreport-about-a-bugreport :)  someone basically should try to write both a straightforward packet-level "throttling" proxy (something that uses python to create a userspace tun/tap network service would do the trick pretty quick) as well as a slightly more complicated HTTP "throttling" proxy (an SSL-capable one): that should be more than enough to act as a repro case for testing purposes.  failing that, seriously: send the engineers to china for a couple of months! :)
►

Sign in to add a comment