Repository navigation
feat: hint whether an event keeps its RDATE - #856
Merged
Merged
Conversation
tobixen
added a commit
that referenced
this pull request
Nov 12, 2026
The three async fallback jobs uninstall niquests, but the tests also import the sync client (caldav.discovery, caldav.testing, test_caldav_unit), which then needs requests. Radicale pulled requests in until 3.9.0; 3.9.1 does not, so all three jobs failed at import on every branch. Install requests explicitly in those jobs. Prompt: merge #855 and #856 Followup-Prompt: yes, [fix the CI breakage, by installing requests in the three async fallback jobs, on its own branch, and merge it first] Assisted-By: Claude Opus 5.5 <noreply@anthropic.com> Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
Zimbra drops every RDATE from an event, timed or all-day, while it keeps an RRULE beside it: seen on Zimbra 8.8 and 10.1 with caldav-server-tester's new probe and by hand. The new hint save-load.event.recurrences.rdate records it, unsupported in the zimbra_8_8 profile, which zimbra_10_1 inherits. Prompt: [about Zimbra 10.1 dropping RDATE only inside the suite's run:] Keep digging. Followup-Prompt: [make recurrence.rdate] as a new feature Assisted-By: Claude Opus 5.5 <noreply@anthropic.com> Reviewed-by: Tobias Brox <tobias@redpill-linpro.com>
tobixen
force-pushed
the
feat/rdate-hint
branch
from
November 12, 2026 19:43
fc45313 to
5bf82a5
Compare
This was referenced Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Commit message:
Zimbra drops every RDATE from an event, timed or all-day, while it
keeps an RRULE beside it: seen on Zimbra 8.8 and 10.1 with
caldav-server-tester's new probe and by hand. The new hint
save-load.event.recurrences.rdate records it, unsupported in the
zimbra_8_8 profile, which zimbra_10_1 inherits.
Prompt: [about Zimbra 10.1 dropping RDATE only inside the suite's run:] Keep digging.
Followup-Prompt: [make recurrence.rdate] as a new feature
Assisted-By: Claude Opus 5.5 noreply@anthropic.com
Needed by PyCalendar/calendaring#53 (its new recurrence.rdate capability reads this hint).