-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.6.0-HF39, 5.8.0-HF22, 6.0
-
Component/s: Nuxeo Drive
-
Sprint:Sprint Drive 5.9.6-1, Sprint Drive 5.9.6-2
-
Story Points:5
For example, let's say Drive requests for changes every 30s:
10:00:00 to 10:00:30 GetChanges
10:00:30 to 10:01:00 GetChanges
10:01:00 to 10:01:30 GetChanges
If a transaction is started 10:00:29, with an event pushed at 10:00:29.350, but the transaction is only committed at 10:00:30.234, the event will be missed.
The event id seems to be auto incremented so would probably be much safer to use.
- depends on
-
NXP-11440 Long running transactions might cause Nuxeo Drive to miss some document updates
- Resolved
-
NXP-11964 Drive > fix random test failure on TestAuditFileSystemChangeFinder#testFindChanges
- Resolved
-
NXP-13811 Fix random failure on drive test TestAuditFileSystemChangeFinder#testFindChanges
- Resolved
- is related to
-
NXDRIVE-1372 Remove some usages of deprecated server-side code
- Resolved
-
NXP-25844 Remove usage of deprecated code and code deprecated since 7.10 or less in nuxeo-drive-server
- Resolved
- is required by
-
NXDRIVE-82 Drive: random failure in test_delete_local_folder_2_clients
- Resolved
-
NXP-15165 Handle deprecation of the old date based audit change summary
- Open
-
NXDRIVE-69 Drive build safety check up
- Resolved
-
NXP-12632 Drive: optimize audit log query
- Open