Can deleting item in instance A causes sync conflict in instance B where item is untouched?

[strandbygaard]

I'm (very) new to Submersion so I'll open this as a discussion, since I don't know if it's just me missing something. Or it could be a minor issue.

I use submersion on both desktop (Mac) and mobile (iPhone). Both current versions pr aug 1st. My dive log was also generated aug 1st. Using Amazon S3 to sync between the two. Time on desktop and mobile synced to the same ntp.

I was noticing that when doing a lot of editing on desktop, I would get sync conflicts when syncing to mobile. Even though I was very careful to only make changes in one place, and only to have one instance running. Specifically to avoid sync conflicts. As sync is notoriously tricky :-)

I always managed to get the sync conflicts to go away on mobile, though it was a bit unclear how. I would say "take remote" to all conflicts but in 2 of 3 occurrences, I was never able to choose "apply" at the end.

I have done some initial poking around the codebase with Claude, which seems to confirm this "deletion causes conflict" behavior (and also that it doesn't have any real implications of note).

Test 1 — peer deletes a dive; local device holds an unedited copy stamped updated
At: 5000000; local lastSync: 4000000:
- conflictsFound > 0 ✓
- status == SyncResultStatus.hasConflicts ✓
- the dive is still there — the deletion did not apply ✓

Test case that claude produced to test my perceived issue

sync_deletion_hlc_gap_test.txt

I'm only just learning how the sync works under the hood, so I'm sure others will know much better than I if this is actually an issue!

[ericgriffin]

Will have a look into this - thanks for the effort you've gone to in detailing it!