Uploaded image for project: 'Nuxeo Drive '
  1. Nuxeo Drive
  2. NXDRIVE-722

Fix Drive synchronization when removing then adding back a filter.

    XMLWordPrintable

    Details

    • Tags:
    • Backlog priority:
      600

      Description

      I open a NXP ticket, not a NXDRIVE one, because the problem does not seem to be related to the Drive client as the bug cannot be reproduced on 8.10, but only on 7.10

      Note that NXP-19482 may be the reason why it is fixed in 8.10
      Maybe a fix can be done in the Drive client to handle the problem, In this case, we will move the ticket to the NXDRIVE project.

      Steps to reproduce:

      1. Configure Drive and wait until sync completes.
      2. Create Folder and Rename to 'Top' in Drive and wait until sync completes
      3. Create Folder and Rename 'Bottom' under 'Top' Folder and wait until sync completes.
        Note: Observe there are two entries in 'RemoteScan' Table.
      4. Apply filter on 'Bottom' Folder ( Uncheck 'Bottom' Folder from 'Select Sync Folder' in Settings)
      5. Wait until 'Bottom' Folder is removed in Drive.
      6. Remove filter on 'Bottom' Folder (check 'Bottom' Folder from 'Select Sync Folder' in Settings)

      Current Behaviour: 'Bottom' Folder is not down synced to drive.
      Expected Behaviour: 'Bottom' Folder should be down synced to drive.

      Root Cause:

      1. On folder creation and rename, forced remote_scan is initiated, but after scan completion entries in 'Remote Scan' is not removed.
      2. On checking the 'Bottom' Folder, the remote scan is initiated on root folder, but due to entries in 'Remote Scan', the remote scan is skipped for 'Top' Folder. Due to this 'bottom' folder is not down synced.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 minute
                  1m

                    PagerDuty