commit | 15e1c3cc5a80b0e328f082b729657b5f21b40a05 | [log] [tgz] |
---|---|---|
author | John Delaney <johnidel@chromium.org> | Tue Jul 30 17:52:08 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jul 30 17:52:08 2024 |
tree | 111aa23c269c2eda89bf9d8c2aa5af5d2e133c24 | |
parent | 759ed8b97de9aa18ad5d50afdb6f2ef37b5f37a7 [diff] |
[ara] Move null report generation to the resolver Why: The null report generation is mostly business logic which storage doesn't need to know about. We expose new APIs on storage to store aggregatable and null reports. Change-Id: I8f3ebab810dd9fdd7a48bb029e38a48a8ab045eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5736034 Commit-Queue: John Delaney <johnidel@chromium.org> Reviewed-by: Andrew Paseltiner <apaseltiner@chromium.org> Cr-Commit-Position: refs/heads/main@{#1334972}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.