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

[Direct Edit] Orphaned documents should first be remotely unlocked before being cleaned up

    XMLWordPrintable

    Details

    • Release Notes Summary:
      Orphaned documents are now unlocked remotely before being cleaned up
    • Release Notes Description:
      Hide

      When the application was shut down while a Direct Edit session was ongoing, the edited document stayed locked on the server and the downloaded file was not removed.
      When starting again, the application will now first retrieve the file's metadatas to unlock the document on the server and then will locally clean up the orphaned file.

      Show
      When the application was shut down while a Direct Edit session was ongoing, the edited document stayed locked on the server and the downloaded file was not removed. When starting again, the application will now first retrieve the file's metadatas to unlock the document on the server and then will locally clean up the orphaned file.
    • Tags:
    • Backlog priority:
      500
    • Sprint:
      nxDrive 11.1.33, nxDrive 11.1.34, nxDrive 11.1.35, nxDrive 11.1.36
    • Story Points:
      2

      Description

      How to reproduce:

      • DirectEdit a document
      • Let Drive autolock the document
      • Close Drive
      • Close the binary editor on the client side
      • Optional: reboot the client side OS...
      • Restart Drive client, which logs e.g.
        2020-04-22 10:04:12 7228 21484 INFO nxdrive.direct_edit Should unlock WindowsPath('C:/Users/<user>/.nuxeo-drive/edit/5d36e8a6-1c47-4ba0-b599-0e6a185860ea_file-content/BIGXLSX.xlsx')

        and does not perform any other action for this document/binary

      • However, when going on the document on the server-side, you can witness the document is still locked.

      Expected result: when the binary is not in use or Drive is restarted, should the locks be held server-side? In most cases, no.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 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 - 2 weeks
                  2w

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.