|
|
Created:
4 years, 3 months ago by Jialiu Lin Modified:
4 years, 3 months ago Reviewers:
vakh (use Gerrit instead) CC:
chromium-reviews, grt+watch_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
Descriptionfix spelling of SBClientMalware.ResourceUrlMatchedBadIp UMA metric
BUG=643539
Committed: https://crrev.com/b39bd2efd5cf400842b08d3de4b9dba83dea4708
Cr-Commit-Position: refs/heads/master@{#416300}
Patch Set 1 #
Messages
Total messages: 16 (7 generated)
The CQ bit was checked by jialiul@chromium.org
The CQ bit was unchecked by jialiul@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
No L-G-T-M from a valid reviewer yet. CQ run can only be started by full committers or once the patch has received an L-G-T-M from a full committer. Even if an L-G-T-M may have been provided, it was from a non-committer, _not_ a full super star committer. See http://www.chromium.org/getting-involved/become-a-committer Note that this has nothing to do with OWNERS files.
Description was changed from ========== fix spelling of UMA metric BUG=643539 ========== to ========== fix spelling of SBClientMalware.ResourceUrlMatchedBadIp UMA metric BUG=643539 ==========
jialiul@chromium.org changed reviewers: + vakh@chromium.org
Hi vakh@, Would you mind take a look at this tiny CL? Thanks!
lgtm
The CQ bit was checked by jialiul@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Committed patchset #1 (id:1)
Message was sent while issue was closed.
Description was changed from ========== fix spelling of SBClientMalware.ResourceUrlMatchedBadIp UMA metric BUG=643539 ========== to ========== fix spelling of SBClientMalware.ResourceUrlMatchedBadIp UMA metric BUG=643539 Committed: https://crrev.com/b39bd2efd5cf400842b08d3de4b9dba83dea4708 Cr-Commit-Position: refs/heads/master@{#416300} ==========
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/b39bd2efd5cf400842b08d3de4b9dba83dea4708 Cr-Commit-Position: refs/heads/master@{#416300}
Message was sent while issue was closed.
drive-by: because you were emitting the previous name, it's good practice to put the old name in histograms.xml with an obsolete tag. Then (i) you can look at the older data and (ii) we'll get alerted if someone else using the same (wrong) name again or (more possibly though still very unlikely), someone else uses something that hashes to the same name. --mark
Message was sent while issue was closed.
On 2016/09/02 at 18:27:56, mpearson wrote: > drive-by: > > because you were emitting the previous name, it's good practice to put the old name in histograms.xml with an obsolete tag. Then (i) you can look at the older data and (ii) we'll get alerted if someone else using the same (wrong) name again or (more possibly though still very unlikely), someone else uses something that hashes to the same name. > > --mark Thanks, Mark. There should not be any data though, since our bad IP list has been empty. (that's also why we did not notice this mistake earlier.) Safe browsing team is planning to add data to this bad ip list soon, so it is an excellent time to get this fixed. |