commit | def69c14c2bc8a02371a7505f8f6a8e6781c8548 | [log] [tgz] |
---|---|---|
author | Laura Peskin <pesk@google.com> | Wed Mar 31 23:08:39 2021 +0000 |
committer | CQ Bot <commit-bot@chromium.org> | Wed Mar 31 23:08:39 2021 +0000 |
tree | 7288bd48c1ddc8cb296ca5b1e463f57ddce1cf79 | |
parent | 4b3ad84d931ab841ba99c23fb81cf8bf939f77f3 [diff] |
[Cobalt 1.1 privacy] Calculate privacy params for StringCounts reports Adds support for StringCounts reports to the registry parser's privacy noise parameter calculator. The sparsity of a StringCounts report is the smaller of: - the total number of cells in a CountMin sketch for the report (currently hard-coded to 50: 5 hashes with 10 cells per hash) - the parent metric's string_buffer_max (if set) times the number of hashes in a CountMin sketch for the report. Change-Id: I61e1b5db0a298841cc9f4ed35a105146b572e890 Reviewed-on: https://fuchsia-review.googlesource.com/c/cobalt/+/507063 Fuchsia-Auto-Submit: Laura Peskin <pesk@google.com> Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com> Reviewed-by: Alexandre Zani <azani@google.com>
Cobalt is a pipeline for collecting metrics data from user-owned devices in the field and producing aggregated reports.
Cobalt includes a suite of features for preserving user privacy and anonymity while giving product owners the data they need to improve their products.
The code in the Git repo at https://fuchsia.googlesource.com/cobalt is known as Cobalt Core. It contains:
In order to have a working Cobalt system you need to also have
//third_party/cobalt
.This document describes how to develop, build and test Cobalt Core independently of Fuchsia.
For example via
git clone https://fuchsia.googlesource.com/cobalt
cd cobalt
./cobaltb.py setup
This will take a few minutes the first time. It does the following:
third_party
dir via Git submodules.sysroot
dir. This uses CIPD.The Python script cobaltb.py
in the root directory is used to orchestrate building and testing Cobalt. It was already used above in ./cobaltb.py setup
.
./cobaltb.py -h
for general helpcobaltb.py <command> -h
for help on a command./cobaltb.py build
The Cobalt build uses GN and ninja.
./cobaltb.py test
./cobaltb.py fmt
./cobaltb.py lint
See: clang-tidy for an explanation of clang-tidy configuration options.
Cobalt uses the Gerrit code review tool. Although Cobalt Core is independent of Fuchsia, we do share infrastructure with Fucshia and so much of the instructions from Fuchsia's Contributing Guide apply to Cobalt Core. The main difference is that Cobalt Core does not use Jiri--it uses Git submodules instead.
Follow the instructions here.
To create a change in Gerrit do the following:
cd ~/cobalt
git checkout -b <branch_name>
git add <files>
git commit
git push origin HEAD:refs/for/master
See the Gerrit documentation for more information.
After creating a change, to upload a patch to your change, do the following:
git add <files>
--amend
option: git commit --amend
git push origin HEAD:refs/for/master