tree 9833a46578d2cfaa242f0f4ba903d70d97f75c7a
parent 5e46ec59eddeb6f3d49b2005e43708bfb405ed90
author Laura Peskin <pesk@google.com> 1617136155 +0000
committer CQ Bot <commit-bot@chromium.org> 1617136155 +0000

[Cobalt 1.1 privacy] Handle unset event_code_buffer_max in
PrivacyEncodingParamsCalculator

If a metric does not have event_code_buffer_max set, the
PrivacyEncodingParamsCalculator now computes the number of
valid event vectors for the metric and uses that as the
effective event_code_buffer_max when computing sparsity.

Bug: 72699
Change-Id: I08260ac98eb2ae0af103bacdc767b6875f0adcd5
Reviewed-on: https://fuchsia-review.googlesource.com/c/cobalt/+/504739
Commit-Queue: Laura Peskin <pesk@google.com>
Reviewed-by: Jared Weinstein <jaredweinstein@google.com>