Skip to content

Tags: tutao/tutanota

Tags

tutanota-release-355.260720.0

Toggle tutanota-release-355.260720.0's commit message
v355.260720.0

tutanota-ios-release-355.260720.0

Toggle tutanota-ios-release-355.260720.0's commit message
v355.260720.0

tutanota-fdroid-release-355.260720.0

Toggle tutanota-fdroid-release-355.260720.0's commit message
v355.260720.0

tutanota-desktop-release-355.260720.0

Toggle tutanota-desktop-release-355.260720.0's commit message
v355.260720.0

tutanota-android-release-355.260720.0

Toggle tutanota-android-release-355.260720.0's commit message
v355.260720.0

tuta-calendar-ios-release-355.260720.0

Toggle tuta-calendar-ios-release-355.260720.0's commit message
v355.260720.0

tuta-calendar-fdroid-release-355.260720.0

Toggle tuta-calendar-fdroid-release-355.260720.0's commit message
v355.260720.0

tuta-calendar-android-release-355.260720.0

Toggle tuta-calendar-android-release-355.260720.0's commit message
v355.260720.0

tutanota-desktop-release-355.260710.0

Toggle tutanota-desktop-release-355.260710.0's commit message

Verified

This commit was signed with the committer’s verified signature.
process delete before put when updating cache by multiple for missed EEs

When syncing an e-mail moved from and back to a given mailSet in a
different client, we send a DELETE event and a CREATE event for the same
MailSetEntry id, as MailSetEntry ids are derived from mail ReceivedDate
and mail id. With 5a8b1d8 we are
putting/deleting instances into the cache by multiple after accumulating
them, and in a given accumulation the temporal order of events is not
respected. This resulted in us putting the MailSetEntry using the CREATE
event, and deleting it right away because of the DELETE event.

This commit fixes that by first doing the deleteMultiple calls and
calling putMultiple for entityUpdates with valid instances.

Co-authored-by: das <das@tutao.de>

tutanota-release-354.260707.0

Toggle tutanota-release-354.260707.0's commit message
v354.260707.0