Sync broken cases

sync_broken_cases.md

Issues awaiting Pull Requests

1. brave/sync#333 (BrianJ, Anthony)

   • device ID potential conflict (more than one device with the same ID)

2. brave/sync#261 (Alexey)

   • Conflict resolution needs to consider timestamps when deciding which record wins
   • brave-core has workaround which is to exclude record from itself

3. When initial setup doesn't complete, sync will remain enabled

   • brave/brave-browser#6098

4. New device to old sync chain takes forever to sync due to huge amounts of records (Jimmy, Anthony)

   • brave/sync#341

Issues having Pull Requests

1. Orphan sync chain, when all devices left sync chain and will never to be used again. (Ev)
   • It affects accuracy of DAU calculation
   • PR in brave/sync#342
2. Consecutive sync record CREATE, UPDATE won't be applied on receiving end (Anthony)
   • brave/brave-browser#6310
   • This blocks migration of brave/brave-browser#5158
   • PR MERGED in brave/brave-core#3602
3. "Other bookmarks" on desktop cause problem for iOS and Android to maintain bookmark consistency (Anthony)
   • brave/brave-browser#5158
   • brave/brave-core#3620 (WIP)
   • brave/brave-browser#6344

Not included in mid November

1. order grows endless if we keep reposition bookmark in front of other (leave this in long term fix)
   1. A, B => B, A (move B) => A, B (move A), ..... so the order would look like (1.0.0.0.0.0.0...0.1 and 1.0.0.0.0...1)
   2. A real world example 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.0.0.0.3.68
   3. This is the trade off of not using UniquePosition but also wants to emit changes for only the moving bookmark
      • It used to recalculate the position of all bookmarks after the one we move
2. Unnecessary resend (brave/brave-browser#6283)
   1. leave and rejoin previous sync chain
      • desktop and iOS
   2. flip sync bookmark toggle off and on