commit | d6809fb4549c9496e05af7559c448349c6c36ff1 | [log] [tgz] |
---|---|---|
author | Ben Reich <benreich@chromium.org> | Thu Apr 04 06:34:07 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 04 06:34:07 2024 |
tree | 0ad4e64cdc5fa86afba496754637110a4d0f408d | |
parent | 3966b91c1b7f5fece270550bed7cdec61a2dffee [diff] |
[FspCache] Update OpenFileSuccess to fallback to GenericSuccess CL:5343674 introduced a new optional callback to the OpenFile FSP method. This required setting up a new OpenFileSuccess operation that enabled passing the result back. In doing so it extended the FSPOperation enum. In the case that the LaCrOS version is running the IDL with the changes from CL:5343674 and Ash is not running with these changes (e.g. LaCrOS is M125+ and Ash is <=124) then the forward will fail (the FSPOperationResponse will default to kUnknown). To avoid this and enable a graceful degradation, this splits out the OpenFileSuccess operation to its own interface method to enable version validation on the mojo remote. In the event the method is not supported it will fall back to a GenericSuccess and strip the supplied base::Value supplied to the callback. Bug: b/331722180 Change-Id: I7b3f8591d9777844da7d0a704724446731707478 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5411572 Reviewed-by: Erik Chen <erikchen@chromium.org> Commit-Queue: Ben Reich <benreich@chromium.org> Reviewed-by: Alexander Bolodurin <alexbn@chromium.org> Cr-Commit-Position: refs/heads/main@{#1282336}
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.