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
It seems like there is a bug where if you pass a from time to schedule.next_occurrences that is close to the DST boundary, you can get future occurrences that occur on the wrong time.
E.g. A recurring appointment that occurs every Sunday at 01:15 am London time. If you call schedule.next_occurrences(from_time) where from_time is just prior to March 27, 2022 01:00 am, all occurrences shift an hour forward to 2:15 am local time.
I created a PR with a failing test that demonstrates the issue. #524
Any help would be appreciated!
The text was updated successfully, but these errors were encountered:
flivni
changed the title
next_occurrences can be wrong when passing from time near DST boundary.
next_occurrences can return incorrect times from time is near DST boundary.
Mar 31, 2022
flivni
changed the title
next_occurrences can return incorrect times from time is near DST boundary.
next_occurrences can return incorrect times when from time is near DST boundary.
Apr 4, 2022
It seems like there is a bug where if you pass a
from
time toschedule.next_occurrences
that is close to the DST boundary, you can get future occurrences that occur on the wrong time.E.g. A recurring appointment that occurs every Sunday at 01:15 am London time. If you call schedule.next_occurrences(from_time) where from_time is just prior to March 27, 2022 01:00 am, all occurrences shift an hour forward to 2:15 am local time.
I created a PR with a failing test that demonstrates the issue.
#524
Any help would be appreciated!
The text was updated successfully, but these errors were encountered: