-
Type: Bug
-
Status: Open
-
Priority: Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: QualifiedToSchedule
-
Component/s: Conflict management, Synchronizer
-
Epic Link:
The scenario described in NXDRIVE-668 should be fixed with the changes made to Drive and the server-side changes made for NXP-21853 and NXP-21854.
Yet we found another bug: when the downstream synchronization is processed to Client-User01, a duplicate can occur:
- subfolder01
- subfolder01__1
This happens when the documentCreated event is the first one in the list of fileSystemItemChanges sent by the server, which is sorted by descending event date.
Happens on OS X that performs the rename first then the create, which becomes the most recent event.
To reveal this bug just uncomment the lines related to "# TODO NXDRIVE-769: uncomment when deduplication issue is fixed" in TestSynchronization:
- test_rename_and_create_same_folder_not_running
- test_rename_and_create_same_file_not_running
- is related to
-
NXDRIVE-777 Remote move not impacted client-side when following the scenario from NXDRIVE-668
- Open
-
NXDRIVE-668 Fix upload issue with changes made while drive client is not running
- Resolved