commit 207cbeebf0d60eefe74efd54bc309aa3595af776
author Mikel Astiz <mastiz@chromium.org> Tue Feb 04 10:13:34 2025
committer Copybara-Service <copybara-worker@google.com> Tue Feb 04 11:39:26 2025
tree b3bb85c7bb102d9a7c3282079bb6fd8e347c8272
parent 8c32e644a35d35b904393407731dc4db8d5993f2

[sync] Remove WipeModelUponSyncDisabledBehavior::kOnceIfTrackingMetadata

See linked bug for detailed background and rationale. The TL;DR is that
this codepath is quite risky, hard to maintain and benefits a very small
number of iOS users. It is time to clean it up, as the consequences for
the few users affected are not too bad either (potential duplication of
data, that they can presumably fix using the available batch upload
flows).

OBSOLETE_HISTOGRAM[Sync.DataTypeClearedOnce]=Logic cleaned up

Change-Id: I9443ae55d5aea15075ceb5a155c739ba22bcce8b
Fixed: 393165673
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6218787
Reviewed-by: Maksim Moskvitin <mmoskvitin@google.com>
Reviewed-by: Marc Treib <treib@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1415455}
NOKEYCHECK=True
GitOrigin-RevId: 3d18ea1eef40e96a38d6b593c31a7d3694c6f1fe