Linus Rath 474eae9992 fix: never duplicate an event's reminders after a busy calendar database #34 ...

A provider that is busy may commit a batch up to a yield point and then
fail it. The engine retried every group of such a batch and relied on
the groups' asserts to refuse one that was already committed, but a
download into an unchanged event asserts only the event's own columns:
when it had only added a reminder or an attendee, the retry added it a
second time.

A download is now planned again from a new read after a failed batch
instead of being sent again, which turns a committed group into an echo.
The fake provider can commit a batch up to a yield point to test it.

2026-09-27 07:53:36 +02:00

..

app

fix: let the user delete or restore held-back deletions from the sync settings #34

2026-09-27 07:19:26 +02:00

calendar

fix: keep syncing a big meeting after it was edited on the phone #34

2026-09-27 07:10:47 +02:00

contacts

fix: keep the groups of a contact created on the device #34

2026-09-27 07:19:27 +02:00

engine

fix: never duplicate an event's reminders after a busy calendar database #34

2026-09-27 07:53:36 +02:00

fakes

fix: never duplicate an event's reminders after a busy calendar database #34

2026-09-27 07:53:36 +02:00

common.test.ts

test: add a fake device provider and jmap server for the sync tests #34

2026-09-27 02:53:22 +02:00

fake-jmap-server.test.ts

test: add a fake device provider and jmap server for the sync tests #34

2026-09-27 02:53:22 +02:00

fake-provider.test.ts

fix: stop reading the read-only flag the contacts provider never returns #34

2026-09-27 05:07:58 +02:00

native.test.ts

feat: give device sync scoped access to the contacts and calendar providers #34

2026-09-27 04:04:00 +02:00

purity.test.ts

test: add a fake device provider and jmap server for the sync tests #34

2026-09-27 02:53:22 +02:00