Issue:
icalBuddy displays wrong ending date for an all-day event beginning on the DST transition day (in the Eastern US timezone). OSX 10.10.
To Replicate:
In iCal / Calendar create an all-day event that begins on Nov 5 2017 and ends on Nov 11 2017. When icalBuddy is subsequently used to print the ending date for this event, it gives the incorrect ending date of Nov 10 2017. Digging deeper, if you ask icalBuddy to print the event using -df %c, you'll see the ending date/time is "Fri Nov 10 23:00:00". This indicates that the DST correction is being incorrectly applied to the ending date (icalBuddy should print the ending date as "Sat Nov 11 00:00:00").
Issue: icalBuddy displays wrong ending date for an all-day event beginning on the DST transition day (in the Eastern US timezone). OSX 10.10.
To Replicate: In iCal / Calendar create an all-day event that begins on Nov 5 2017 and ends on Nov 11 2017. When icalBuddy is subsequently used to print the ending date for this event, it gives the incorrect ending date of Nov 10 2017. Digging deeper, if you ask icalBuddy to print the event using
-df %c, you'll see the ending date/time is "Fri Nov 10 23:00:00". This indicates that the DST correction is being incorrectly applied to the ending date (icalBuddy should print the ending date as "Sat Nov 11 00:00:00").Possibly related to #3.