commit | d5c39c6fa5e8f77b47202ff34de2ed2b4684ab28 | [log] [tgz] |
---|---|---|
author | Jon Toohill <jtoohill@google.com> | Wed Aug 13 22:12:10 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 13 22:12:10 2025 |
tree | a6109c043ae37b087fb07ce32ec69f9d9a065573 | |
parent | bf0180792013c313b16e5ca9650a32c443c00e82 [diff] |
[M140] Log TokenEvents for orphaned tokens Original change's description: > Log TokenEvents for orphaned tokens > > Adds a separate event type to record tokens that were not spent but also > had not expired at the time the token cache was destroyed. This can be > inferred from Issued - (Expired + Spent), but it's helpful to make it > explicit, since a discrepancy could reveal some other scenario where > tokens are lost. > > For now, we record the orphaned tokens directly in the > IpProtectionTokenManagerImpl dtor. Later we can try sending them back to > the browser process and recording them there instead. > > Bug: 435240740 > Change-Id: Id9b600339b814b8c3f31db00063d57cb626a17ef > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6820056 > Commit-Queue: Chad Duffin <chadduffin@chromium.org> > Reviewed-by: Zainab Rizvi <rizvis@google.com> > Auto-Submit: Jon Toohill <jtoohill@google.com> > Reviewed-by: Andrew Williams <awillia@chromium.org> > Reviewed-by: Chad Duffin <chadduffin@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1498897} Bug: 438535033,435240740 Change-Id: Id9b600339b814b8c3f31db00063d57cb626a17ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6845904 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Chrome Cherry Picker <chrome-cherry-picker@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/7339@{#545} Cr-Branched-From: 27be8b77710f4405fdfeb4ee946fcabb0f6c92b2-refs/heads/main@{#1496484}
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.