You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to the same underlying reason explained in #3185, concurrently updating a list field of a sample held in-memory in multiple processes can cause data loss.
Note that this is only an issue if a sample object is held in-memory in one process while being edited in another process, which is not as common as #3185.
Ideally this would be fixed by Document._save() intelligently performing array updates using $push, $pull, etc rather than $set-ing the entire field:
Due to the same underlying reason explained in #3185, concurrently updating a list field of a sample held in-memory in multiple processes can cause data loss.
Note that this is only an issue if a
sample
object is held in-memory in one process while being edited in another process, which is not as common as #3185.Ideally this would be fixed by
Document._save()
intelligently performing array updates using$push
,$pull
, etc rather than$set
-ing the entire field:fiftyone/fiftyone/core/odm/document.py
Line 671 in 3026474
But unfortunately mongoengine does not natively support this:
https://docs.mongoengine.org/guide/document-instances.html#saving-and-deleting-documents
TERMINAL A
TERMINAL B
The text was updated successfully, but these errors were encountered: