handle NEW/NEW conflicts by being real conflicts
authorMatthieu Gallien <matthieu.gallien@nextcloud.com>
Wed, 16 Oct 2024 13:06:13 +0000 (15:06 +0200)
committerMatthieu Gallien <matthieu.gallien@nextcloud.com>
Thu, 17 Oct 2024 07:45:57 +0000 (09:45 +0200)
commitf0908dbbfc0eaaf07a00cf7363d1f4e804025b09
tree079aa0671471405e2f43cbc2f2711c9efce72633
parent7301ad335685435287498aa767355940ecd66c5b
handle NEW/NEW conflicts by being real conflicts

NEW/NEW conflicts could sometime be ignored and replaced by update
metadata instructions

we stop doing this and handle them like any other conflicts

that would cause more download from the server

those conflicts would be solved automatically in case this is not a real
conflict but the client was missing the server reply with the updated
metadata

will enable more changes to improve MOVE detection from server side

Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
src/libsync/discovery.cpp
test/testchunkingng.cpp
test/testsyncengine.cpp