Bug #99053 for Data-ICal: 8pm bug

Mon Sep 22 11:25:31 2014 steve.dickinson [...] cello.com - Ticket created

Subject:	8pm bug
Date:	Mon, 22 Sep 2014 11:25:28 -0400
To:	bug-Data-ICal [...] rt.cpan.org
From:	Steve Dickinson <steve.dickinson [...] cello.com>

I think I just discovered a bug in the Data::ICal:Entry:Event. If my start date happens to be 8pm, I get this result in the calendar attachement (I'm setting the end date to +1 hour of the start date): DTEND:20141002T010000Z DTSTART:20141002Z DTSTART should be getting set to 20141002T000000Z but the time piece is missing entirely.This causes strange things to happen when a user tries to actually use the calendar attachment. On my android device I kept getting a "Describe error". Thanks, Steve

Mon Feb 16 23:25:40 2015 cpan [...] chmrr.net - Status changed from 'new' to 'rejected'

Mon Feb 16 23:25:45 2015 alex [...] chmrr.net - Correspondence added

Subject:	Re: [rt.cpan.org #99053] 8pm bug
Date:	Mon, 16 Feb 2015 23:25:28 -0500
To:	bug-Data-ICal [...] rt.cpan.org
From:	Alex Vandiver <alex [...] chmrr.net>

On Mon, 22 Sep 2014 11:25:32 -0400 "Steve Dickinson via RT" <bug-Data-ICal@rt.cpan.org> wrote: Show quoted text

> I think I just discovered a bug in the Data::ICal:Entry:Event. If my > start date happens to be 8pm, I get this result in the calendar > attachement (I'm setting the end date to +1 hour of the start date): > > DTEND:20141002T010000Z > DTSTART:20141002Z

Data::ICal doesn't do any date math; this is caused by whatever you're using to generate the date strings. Namely, whatever it is is omitting the time part of the datetime when it is midnight GMT -- since you're apparently in US/Eastern, that happens to currently be 8pm local time - Alex