system_api: Add the churn_active_status in preserved file

Preserve the churn active status history into preserved file.

BUG=chromium:1386189
TEST=USE=test emerge-dedede chromeos-base/system_api

Change-Id: I2b07816bc1026990a4a80af22f13a7dba4cf68ba
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/4223256
Tested-by: Eric Wang <qianwan@google.com>
Reviewed-by: Hirthanan Subenderan <hirthanan@google.com>
Commit-Queue: Eric Wang <qianwan@google.com>
NOKEYCHECK=True
GitOrigin-RevId: f4535287f2bbd22b13d34e0563b4e035be14b342
1 file changed
tree: 919421b50a2cd5e0eb27fc36e8c7573fed6809fe
  1. constants/
  2. dbus/
  3. mojo/
  4. src/
  5. switches/
  6. .gitignore
  7. BUILD.gn
  8. build.rs
  9. Cargo.toml
  10. DIR_METADATA
  11. LICENSE
  12. OWNERS
  13. README.md
  14. system_api.pc
README.md

This directory (platform2/system_api) contains constants and definitions like D-Bus service names that are shared between Chromium and Chromium OS.

This directory is only for things like headers and .proto files. No implementation should be added.

When writting a .proto file make sure to use:

option optimize_for = LITE_RUNTIME;

This will force usage of a lite protobuf instead of a full/heavy weight protobuf. The browser only links against the light version, so you will get cryptic link errors about missing parts of Message if you define a protobuf here and then try to use it in Chrome. Currently CrOS links against the full protobuffer library, but that might change in the future.

When declaring a protobuf, avoid use of required unless it is exactly what you mean. "Required is Forever" and very rarely should actually be used. Consult Protocol Buffer Basics: C++ for a detailed of this issue.