-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 2.1.1130
-
Fix Version/s: 3.0.6
-
Component/s: Synchronizer
-
Epic Link:
-
Backlog priority:700
- User1 Drive: Configure nuxeo-drive
- User2 DM: Create a folder 'top' and a child folder 'top\sub'
- User2 DM: Import file1 and file2 to 'top' folder and then file3 and file4 to 'top\sub' folder
- User2 DM: Share the 'top' folder with User1 with read access. Ensure User1 does not have write access to this folder in any manner (ex: group share).
- User1 DM: Login to DM
- User1 DM: Enable 'sync' for the user1 workspace for user1.
- User1 DM: Search for folder 'top'. Then enable 'sync' for the 'top' folder for user1.
- User1 Drive: Wait for drive to sync both the workspace and the 'top' folder to local PC.
- User1 Drive: Verify all the subfolders and files are synced properly.
- User2 DM: rename the 'sub' folde as 'sub2'
- User1 Drive: Wait for the drive to sync the changes (sub will be renamed as sub2)
- User1 Drive: Now delete the file 'top\sub2\file3' in local PC
- User1 Drive: Confirm that Drive shows a notification in the system tray that a readonly file is deleted.
- User1 Drive: Open settings dialog for nuxeo-drive and then click on 'Select Sync Folders' button.
- User1 Drive: The 'filters' window will open and it shows that the 'top\sub2\file3' is unchecked.
- User1 Drive: Now 'check' the file3 and click ok.
Expected Result: Since file3 is marked for sync, the file3 should download from server to local PC again.
Actual Result: file3 is not syncing to local PC for user1.
The step 10 above the most crucial step. Without this step the bug will not reproduce.
Seems like after that the Drive client (at least on OSX) didn't stop synching.
After stop and start of the client, unchecking then checking again the file3.txt file did in fact synch it again.