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
In order to use recurring events for editing as described in the readme, the sequence number MUST be set to the highest one in the UID. That should be done automatically.
The way we interpret the events, we interpret them based on the latest SEQUENCE. As such, SEQUENCE should be set to the value of our assumption to mitigate exposing details and problems to users.
To Reproduce
If the sequence number of the edited event is lower than the sequence number of the base (or another event), then it is not treated as an update.
Describe the bug
In order to use recurring events for editing as described in the readme, the sequence number MUST be set to the highest one in the UID. That should be done automatically.
The way we interpret the events, we interpret them based on the latest SEQUENCE. As such, SEQUENCE should be set to the value of our assumption to mitigate exposing details and problems to users.
To Reproduce
If the sequence number of the edited event is lower than the sequence number of the base (or another event), then it is not treated as an update.
ICS file
Expected behavior
I would expect nextcloud to send an invite but it does not.
Console output
Version:
Additional context
This concerns caldav scheduling
Suggested implementation
python-recurring-ical-events/test/calendars/issue-15-duplicated-events.ics
Line 1 in f4a90b2
python-recurring-ical-events/test/test_issue_15.py
Line 21 in f4a90b2
The text was updated successfully, but these errors were encountered: