Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Recurring events created in DST are off by an hour after DST
See original GitHub issueI’ll start by saying that this feels like a bug but maybe it’s user error?
I have an event with this date (12:10PM)
DTSTART;TZID=America/New_York:20190922T121000
Becomes 11:10AM when filtering events with event.rrule.between() on 3-Nov.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:8 (2 by maintainers)
Top Results From Across the Web
All events shifted one hour after Daylight savings.
All my Calendar events have shifted an hour earlier. I've checked the timezone and verified it is correct, and read other posts on...
Read more >Recurring Events and Daylight Saving Time
When a calendar (such as Pocket Informant, Apple Calendar, Google Calendar, etc) expands a repeating event, it follows the DST rules of the...
Read more >Daylight saving causes recurring meetings to be 1 hour off #67
I have recurring meetings with clients in EST which added 1 hour this week for DST. When the recurring event was created the...
Read more >Recurring events showing incorrect time after Daylight ...
All the recurring events. The only events that are displaying correctly, at the same time before and after DST, are ones that aren't...
Read more >Meeting Requests and Appointments are Off by One Hour
If the time on the Day/Week calendar is off by one hour the week after DST changed, also see Daylight Saving Time Calendar...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
sorry, that was a translation mistake, I meant “might”, not “eventually” (which, directly translated to German, means “might” 😄 ).
But bottom line: In my experience the fork does not solve this issue.
FYI: The issue I mentioned said that it might solve the issue. TBC