commit | fcd670349f4d6d42a15acc13e5499608ee98854b | [log] [tgz] |
---|---|---|
author | Camillia Smith Barnes <cammie@chromium.org> | Tue Apr 01 00:28:31 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 01 00:28:31 2025 |
tree | 633638e6373989a67b000a91258e93d773eda840 | |
parent | f37072578e92ec3b57c4a21bc225a67fdac24279 [diff] |
Shared Storage: Make << escape SharedStorageEventParams serialized_data We update the operator<< overload for SharedStorageEventParams so that it escapes SharedStorageEventParams::serialized_data, as serialized_data is not necessarily valid UTF-8. Moreover, some of the bytes in serialized_data may be interpreted as ASCII control characters, which can end up overwriting other parts of the struct that are supposed to be serialized to the ostream by <<. Hence, we now escape the serialized data when used by <<. At this point, this is a cosmetic change that only affects tests, making it easier to debug them, since values of SharedStorageEventParams will now serialize to the terminal more intuitively when they don't meet expectations. Bug: 401011862 Change-Id: Iad117047e7b1b843c4d8059f8230a454c4985353 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6417209 Commit-Queue: Cammie Smith Barnes <cammie@chromium.org> Reviewed-by: Yao Xiao <yaoxia@chromium.org> Cr-Commit-Position: refs/heads/main@{#1440655}
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.