Google Git
Sign in
chromium / chromium / src / components / feedback / redaction_tool / 4d0bef644311ff233df2687d3be90ecc2188fa1f
commit4d0bef644311ff233df2687d3be90ecc2188fa1f[log] [tgz]
authorRohit Kapoor <rohkap@google.com>Wed May 15 18:53:55 2024
committerCopybara-Service <copybara-worker@google.com>Wed May 15 19:01:41 2024
treeed2bfda687d7844d2ee667ec9360c54361db3f12
parent89e0ffb9a25633b33a55bf89c4563c8128feeaa9 [diff]
Redaction Tool: Redaction Tool Caller Metric: Breakdown the Feedback Tool and Crash Tool metrics into components for easier analysis.

Bug: 338447818
Change-Id: I8a91345618967e62e0f1dfcc67376515d5063ca4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5535317
Reviewed-by: Xiangdong Kong <xiangdongkong@google.com>
Reviewed-by: Jimmy Gong <jimmyxgong@chromium.org>
Commit-Queue: Rohit Kapoor <rohkap@google.com>
Cr-Commit-Position: refs/heads/main@{#1301473}
NOKEYCHECK=True
GitOrigin-RevId: c88e857c6d4a5c36eaff483d0d70ac439b0a691c
3 files changed
tree: ed2bfda687d7844d2ee667ec9360c54361db3f12
  1. test_data/
  2. BUILD.gn
  3. inprocess_metrics_recorder.cc
  4. inprocess_metrics_recorder.h
  5. inprocess_metrics_tester.cc
  6. inprocess_metrics_tester.h
  7. ip_address.cc
  8. ip_address.h
  9. metrics_tester.h
  10. pii_types.h
  11. README.md
  12. redaction_tool.cc
  13. redaction_tool.h
  14. redaction_tool_metrics_recorder.h
  15. redaction_tool_unittest.cc
  16. url_canon.h
  17. url_canon_internal.cc
  18. url_canon_internal.h
  19. url_canon_ip.cc
  20. url_canon_ip.h
  21. url_canon_stdstring.cc
  22. url_canon_stdstring.h
  23. url_parse.h
  24. validation.cc
  25. validation.h
README.md

redaction_tool: PII Redaction Tool

A redaction_tool redacts the following PII using a wide set of RegEx expressions: kAndroidAppStoragePath kEmail kGaiaID kIPPAddress kIPAddress kLocationInfo kMACAddress kUIHierarchyWindowTitles kURL kSerial kSSID kStableIdentifier kVolumeLabel

The cros/upstream/main branch is a mirror of the components/feedback/redaction_tool directory from upstream.

How to update the source

To pull in updates from chromium/src, do the following:

  • git remote update

  • git checkout -b main cros/main

  • git merge cros/upstream/main

    • BUILD.gn should mostly use the version from main, unless the upstream changes the files to be built.
    • The #include paths should use the version from main (without “components/feedback”). This should be the majority of the merge conflicts.
    • In the commit message of the merge, list the commits from upstream that are merged.
    • If you need to do make changes to the merged commits (outside of conflicts), do that work in separate commits. For example, if you need to revert commits, use git revert after committing the merge commit. This preserves the history and makes it clear why a change is being reverted rather than quietly changing it in the merge commit.
    • Check the changes introduced by your merge by doing a diff against the commit before the merge. The difference should be the same as the changes in the upstream.

  • Push the resulting merge commit with:

    (chroot) $ git push HEAD:refs/for/main