-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: 5.6.0-HF39
-
Fix Version/s: 5.6.0-HF40, 5.8.0-HF27, 6.0-HF01, 7.1
-
Component/s: Nuxeo Drive
Because the document is adapted as a FileSystemItem by the defaultSyncRootFolderItemFactory when logged as a virtual deletion event in the audit log by the NuxeoDriveFileSystemDeletionListener.
This is due to the fact that we relax the sync root constraint to allow security update detection, see NXP-13119 and especially https://github.com/nuxeo/nuxeo-drive-server/commit/b1ba6c7
Thus the id sent to Drive starts with the wrong factory for userA: defaultSyncRootFolderItemFactory instead of defaultFileSystemItemFactory, then the item is not found in the local database when updating remote states, see Synchronizer._update_remote_states:
doc_pair = session.query(LastKnownState).filter_by( local_folder=server_binding.local_folder, remote_ref=remote_ref).first()
- depends on
-
NXP-13119 Take into account a security update in the audit change finder
- Resolved
- is required by
-
NXDRIVE-167 Relax constraint on factory name in FileSystemItem id to match 'deleted' or 'securityUpdated' events when updating remote states
- Resolved
-
NXP-16478 Fix drive root unsync when synchronizing parent root
- Resolved