[SashankBhamidi]

Three bugs in what ships, found while planning what's next.

• An edit the server won't take stopped every sync. A 403, 400 or 415, or a JMAP forbidden, left the push in flight, and every sync after raised at it. Now it's a NOT_ALLOWED conflict with the server's reason in Conflict.reason, and the rest of the pushes still go out.
• Cyrus and Baïkal add SCHEDULE-STATUS to the attendees of an event you organize, so your own write came back as a remote change. The CalDAV fingerprint now leaves out SCHEDULE-STATUS and SCHEDULE-FORCE-SEND.
• A refused change was taken as news when the server reported the synced copy at a new version, so it went out again. It stays refused now.

New: NotAllowed, ConflictKind.NOT_ALLOWED, Conflict.reason and Record.is_refused_for_key. Renamed: Record.is_refused_change to is_refused_existing, since it covers deletes too. New column conflict_reason, schema version 1 edited in place.

The JMAP adapter checks a SetError's properties itself until PyCalendar/calendaring-jmap#94 lands. The probes are in #46.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[read-the-docs-community]

Documentation build overview

📚 calendaring-sync | 🛠️ Build #35723708 | 📁 Comparing 88c2ca5 against latest (f0fc9e7)

  🔍 Preview build  

21 files changed · ± 21 modified

± Modified

• genindex.html
• explanation/adapters.html
• explanation/design.html
• how-to/conflicts.html
• how-to/errors.html
• how-to/write-an-adapter.html
• reference/adapters.html
• reference/glossary.html
• reference/guarantees.html
• reference/objects.html
• and 11 more...