Tickets :: [#13064] Invalid DURATION for ALARM triggers

6.0.0-alpha14

6/25/25

Summary	Invalid DURATION for ALARM triggers
Queue	Kronolith
Queue Version	Git master
Type	Bug
State	Resolved
Priority	2. Medium
Owners	jan (at) horde (dot) org
Requester	marten (at) dmfs (dot) org
Created	03/20/2014 (4115 days ago)
Due
Updated	03/26/2014 (4109 days ago)
Assigned	03/21/2014 (4114 days ago)
Resolved	03/26/2014 (4109 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

03/26/2014 12:51:24 PM	Git Commit	Comment #8	Reply to this comment
Changes have been made in Git (FRAMEWORK_5_1): commit 51d86a0387bbfec2340e90d6043e3484ba38409e Author: Jan Schneider <jan@horde.org> Date: Wed Mar 26 13:51:09 2014 +0100 [jan] Fix TRIGGER generation if alarm value is negative (~~Bug #13064~~). kronolith/docs/CHANGES \| 1 + kronolith/package.xml \| 2 ++ 2 files changed, 3 insertions(+), 0 deletions(-) http://github.com/horde/horde/commit/51d86a0387bbfec2340e90d6043e3484ba38409e

03/26/2014 12:51:21 PM	Git Commit	Comment #7	Reply to this comment
Changes have been made in Git (FRAMEWORK_5_1): commit f5a3c6ae959c2ca29c42a3a02b80f3c5fe4ee9ce Author: Jan Schneider <jan@horde.org> Date: Wed Mar 26 13:43:10 2014 +0100 Fix TRIGGER generation if alarm value is negative. We don't support negative alarm values, i.e. alarms after the event start, natively, but they may be added from external clients and work fine otherwise. ~~Bug: 13064~~ kronolith/lib/Event.php \| 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) http://github.com/horde/horde/commit/f5a3c6ae959c2ca29c42a3a02b80f3c5fe4ee9ce

03/26/2014 12:45:49 PM	Jan Schneider	Assigned to Jan Schneider State ⇒ Resolved

03/26/2014 12:45:41 PM	Git Commit	Comment #6	Reply to this comment
Changes have been made in Git (master): commit 1fbcd0f75d8089457c281d5e37920960e2e54a37 Author: Jan Schneider <jan@horde.org> Date: Wed Mar 26 13:43:10 2014 +0100 Fix TRIGGER generation if alarm value is negative. We don't support negative alarm values, i.e. alarms after the event start, natively, but they may be added from external clients and work fine otherwise. ~~Bug: 13064~~ kronolith/lib/Event.php \| 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) http://github.com/horde/horde/commit/1fbcd0f75d8089457c281d5e37920960e2e54a37

03/24/2014 09:14:42 PM	marten (at) dmfs (dot) org	Comment #5	Reply to this comment
Can you provide an event from the kronolith DB that triggers this? You mean other than the exported VCALENDAR object? How do can one get that? Via SQL dumps of the kronolith_events table. The event_id value should be take from the vcalendar object's id. Sorry, I won't be able to provide a dump. I have to rely on the user who reported it, but he didn't send any. I think you should be able to reproduce the issue when you create an all-day event and set the alarm to 8:00 on the day of the event (i.e. the alarm should fire after the event started)

03/21/2014 09:49:39 AM	Jan Schneider	Comment #4	Reply to this comment
Can you provide an event from the kronolith DB that triggers this? You mean other than the exported VCALENDAR object? How do can one get that? Via SQL dumps of the kronolith_events table. The event_id value should be take from the vcalendar object's id.

03/21/2014 09:20:37 AM	marten (at) dmfs (dot) org	Comment #3	Reply to this comment
Can you provide an event from the kronolith DB that triggers this? You mean other than the exported VCALENDAR object? How do can one get that? I'll have to ask the user who reported this issue.

03/21/2014 09:04:35 AM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
Can you provide an event from the kronolith DB that triggers this?

03/20/2014 09:21:35 PM	marten (at) dmfs (dot) org	Comment #1 Milestone ⇒ State ⇒ Unconfirmed Patch ⇒ No Queue ⇒ Kronolith Summary ⇒ Invalid DURATION for ALARM triggers Type ⇒ Bug Priority ⇒ 2. Medium	Reply to this comment
Check out this event created by Horde: BEGIN:VCALENDAR VERSION:2.0 X-WR-CALNAME:Kalender von xxxxxxxxxxxxx@yyyyyyyyyy PRODID:-//The Horde Project//Horde iCalendar Library//EN BEGIN:VEVENT DTSTART;VALUE=DATE:19670618 DTEND;VALUE=DATE:19670619 X-FUNAMBOL-ALLDAY:1 DTSTAMP:20140320T100527Z UID:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx CREATED:20140319T202551Z LAST-MODIFIED:20140319T202551Z SUMMARY:xxxxxx DESCRIPTION:1967 CLASS:PUBLIC STATUS:CONFIRMED TRANSP:OPAQUE RRULE:FREQ=YEARLY;INTERVAL=1 BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:xxxxx TRIGGER;VALUE=DURATION:-PT-480M END:VALARM END:VEVENT END:VCALENDAR As you can see the Alarm trigger is invalid and should read as "PT480M" instead (since it's supposed to start at 8:00 on the day of the event).