-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.4.0
-
Fix Version/s: 4.4.4
-
Component/s: Direct Edit, Lock / Autolock
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.
- depends on
-
NXPY-172 Always log the server response
- Resolved
- Is referenced in