Fix processor stop before initial sync done
From the bridge's perspective, it's confusing to receive ApplyStopSyncChanges() with a non-null parameter, which reflects sync being disabled, without a prior MergeSyncData() call, which represents sync being enabled. Instead, make sure that a null parameter is passed to the bridge if the initial sync is not done. Prior to this patch, bridges would be overly conservative and clear sync metadata unnecessarily (because there couldn't be any). Other than that, no real user-facing issue exists. Credits for feuunk@ for surfacing and investigating the scenario. Bug: 890709 Change-Id: Ic39fb83596bd4e5e4c6f921b2df0812d0d94515c Reviewed-on: https://chromium-review.googlesource.com/c/1288578Reviewed-by:Florian Uunk <feuunk@chromium.org> Commit-Queue: Mikel Astiz <mastiz@chromium.org> Cr-Commit-Position: refs/heads/master@{#600884}
Showing
Please register or sign in to comment