commit | dea28be7553384382c46b124dab8edc38bb60c32 | [log] [tgz] |
---|---|---|
author | Marc Treib <treib@chromium.org> | Fri Jul 12 06:15:55 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jul 12 06:15:55 2024 |
tree | 123c7773dcf3c6347e21fbaf2813291cc986fd45 | |
parent | 8b41b33e535322ee511615381025b5a030d544da [diff] |
Sync: Implement GetTypesWithUnsyncedData off the sync sequence Before this CL, the implementation of GetTypesWithUnsyncedData involved the sync sequence (ultimately, the data came from ModelTypeWorker). This was nice and simple, but didn't work well when the sync sequence was busy, most notably during initial sync. This CL replaces that implementation with one that avoids the sync sequence entirely. It instead gets the data directly from the model thread(s), via ModelTypeController -> ModelTypeControllerDelegate (aka processor). There is one change (in addition to not blocking on the sync sequence): The behavior in case of ModelErrors. Previously, types that have encountered a ModelError would not report any unsynced changes. Now they will report them. This will rarely make a difference (after all, ModelErrors are hopefully rare!) but seems like an improvement. Bug: 349970109 Change-Id: I50e4e860242283e7b3498c510e2bbb3d8788dcc1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5683369 Commit-Queue: Marc Treib <treib@chromium.org> Reviewed-by: Mikel Astiz <mastiz@chromium.org> Auto-Submit: Marc Treib <treib@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1326570}
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.