You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The merge proceeds normally because there is no corresponding entry in A's branch (there is only a tombstone after the file was moved). However, as merge preserves blob ids, the merge begins to overwrite the renamed file, resulting it data loss.
Ideas for fix:
When this situation occurs, generate a new blob_id for the dst file of the merge
Consider two replicas A and B:
A
creates a fileB
syncs and merges withA
A
renames / moves the fileB
updates the fileA
syncs withB
and starts to mergeThe merge proceeds normally because there is no corresponding entry in
A
's branch (there is only a tombstone after the file was moved). However, as merge preserves blob ids, the merge begins to overwrite the renamed file, resulting it data loss.Ideas for fix:
Related to #70
The text was updated successfully, but these errors were encountered: