-
Notifications
You must be signed in to change notification settings - Fork 233
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
UNTIL
not handled correctly if it falls into a DST change
#736
Labels
Comments
minichma
added a commit
that referenced
this issue
Feb 23, 2025
minichma
added a commit
that referenced
this issue
Feb 23, 2025
Nice! Was this the result a systematic approach or was it more of a coincidence? |
Actually, while trying to migrate our project to v5, I'm trying to remove many of the workarounds that were required with v4, but now some tests start failing. That's how I identify these edge cases. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
UNTIL
not handled correctly if it falls into a DST change.The following VEVENT should produce two occurrences, but it produces only one:
The expected occurrences are at
20201024T023000
and20201025T023000
but the latter is not returned. I.e.20201025T023000
exists twice in CET due to a DST change at 3:00 back to 2:00.Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: