Closed
Bug 1377983
Opened 7 years ago
Closed 7 years ago
Remove comparative V2/V4 Application Reputation telemetry probes
Categories
(Toolkit :: Safe Browsing, enhancement, P2)
Toolkit
Safe Browsing
Tracking
()
RESOLVED
FIXED
mozilla56
Tracking | Status | |
---|---|---|
firefox56 | --- | fixed |
People
(Reporter: francois, Assigned: tnguyen)
References
Details
(Whiteboard: #sbv4-m8)
Attachments
(1 file)
We should remove these probes since we are no longer running V2 and V4 in parallel on Nightly: - APPLICATION_REPUTATION_ALLOWLIST_MATCH - APPLICATION_REPUTATION_BLOCKLIST_MATCH The code using these probes was removed in bug 1366965 so all that's left is to take this out of Histograms.json.
Reporter | ||
Comment 1•7 years ago
|
||
Thomas, are you able to prepare a quick patch for this? I'd do it myself but then I won't be able to review it :)
Assignee: nobody → tnguyen
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Comment hidden (mozreview-request) |
Assignee | ||
Comment 3•7 years ago
|
||
sure, I checked blame and they are mistakenly added in bug 1297167. Removed them.
Reporter | ||
Comment 4•7 years ago
|
||
mozreview-review |
Comment on attachment 8883149 [details] Bug 1377983 - Remove comparative V2/V4 Application Reputation telemetry probes https://reviewboard.mozilla.org/r/154086/#review159216 r+ and datareview+
Attachment #8883149 -
Flags: review?(francois) → review+
Pushed by fmarier@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0a03457de72b Remove comparative V2/V4 Application Reputation telemetry probes r=francois
Reporter | ||
Comment 6•7 years ago
|
||
(In reply to Thomas Nguyen[:tnguyen] ni plz from comment #3) > sure, I checked blame and they are mistakenly added in bug 1297167. Removed > them. Ah, that's why the blame was so weird. Nice investigation :)
Comment 7•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/0a03457de72b
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox56:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla56
You need to log in
before you can comment on or make changes to this bug.
Description
•