-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.3.1107
-
Fix Version/s: 1.3.1216
-
Component/s: Direct Edit
-
Sprint:Sprint Drive 7.1-2
-
Story Points:5
This use case is buggy, typically :
- Edit a document => synchronizes it under Locally Edited
- Register its parent folder ('Test WS') as a sync root => 'Test WS' is synchronized with the file inside it
- Edit the document from the Locally Edited folder on the file system
=> it is well updated server-side, but locally it is removed from Locally Edited and created inside 'Test WS' with the deduplication suffix __1
Note that at last step if we edit the file locally from 'Test WS' there is no problem.
Other scenario:
- Edit a document from a synchronized folder
- Update its content from the server
=> Content is updated under the Locally Edited folder but not under 'Test WS'
We should probably handle all doc pairs with the FileSystemItem id sent by the server in the remote changes instead of the first one only.
See Synchronizer._update_remote_states:
doc_pair = session.query(LastKnownState).filter_by( local_folder=server_binding.local_folder, remote_ref=remote_ref).first()
=> use .all() instead of first()?
- depends on
-
NXDRIVE-175 Some remote changes aren't detected because of modification time rounded down ot the second
- Resolved
- is required by
-
NXDRIVE-176 Random failure at line 34, in test_drive_edit_non_synced_doc: NPE in DownloadServlet
- Resolved
-
NXDRIVE-187 Drive Edit of a document by a user different from the last contributor generates a conflict
- Resolved
-
NXDRIVE-126 Write functional tests about Drive Edit
- Resolved