-
Notifications
You must be signed in to change notification settings - Fork 393
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cancelled Occurrence replaced by a new Event/Occurrence causes occurrences_after to fail #562
Comments
Continuing to investigate my own issue, the problem is linked to the Based on some notes from here:
Potentially just added the Thoughts? |
For the record, having posted this the solutions became easier to solve, the On a very simple basis:
The only additions being the three |
Where there is an Event with a cancelled Occurrence, but another Event has been scheduled in place of the original at the same time, it causes
EventListManager.occurrences_after()
to fail atnext_occurrence = heapq.heappop(occurrences)[0]
with an'<' not supported between instances of 'generator' and 'generator'
error.Part of the issue seems to be that
EventListManager.occurrences_after()
doesn't employ the same logic asEvent.get_occurrences()
to work persistedoccurrences
into thegenerator
set.For example, in a case where an
Event
has only a singleOccurrence
and that Occurrence is cancelled, how should that be treated here? In either case, it causesoccurrences_after()
to fail which isn't the correct behaviour.The use of
OccurrenceReplacer
happens at the end, but it has already failed due to matchOccurrences
being added to theheap.
The text was updated successfully, but these errors were encountered: