Tickets :: [#7580] Alarms triggering too early

6.0.0-beta1

7/5/25

Summary	Alarms triggering too early
Queue	Horde Framework Packages
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	2. Medium
Owners	chuck (at) horde (dot) org, jan (at) horde (dot) org
Requester	chuck (at) horde (dot) org
Created	10/28/2008 (6094 days ago)
Due
Updated	11/24/2008 (6067 days ago)
Assigned
Resolved	11/24/2008 (6067 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

11/24/2008 02:02:09 AM	Chuck Hagenbuch	Comment #5 State ⇒ Resolved	Reply to this comment
Fixed.

11/24/2008 01:59:43 AM	CVS Commit	Comment #4	Reply to this comment
Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/framework/Alarm/Alarm/sql.php?r1=1.14&r2=1.15&ty=u http://cvs.horde.org/diff.php/horde/docs/CHANGES?r1=1.1178&r2=1.1179&ty=u

10/28/2008 05:48:58 AM	Chuck Hagenbuch	Comment #3	Reply to this comment
This (perhaps predictably) results in snoozing not working either.

10/28/2008 05:45:12 AM	Chuck Hagenbuch	Comment #2	Reply to this comment
It's probably Horde_Alarm, because Nag isn't showing the task as overdue until the correct time.

10/28/2008 05:41:58 AM	Chuck Hagenbuch	Comment #1 Priority ⇒ 2. Medium Patch ⇒ No Milestone ⇒ Assigned to Jan Schneider Assigned to Chuck Hagenbuch Queue ⇒ Horde Framework Packages Summary ⇒ Alarms triggering too early Type ⇒ Bug State ⇒ Assigned	Reply to this comment
I'm not actually sure if this is a Horde_Alarm or Nag problem, but task alarms are triggering as soon as it's the day they're set for, not waiting until the hours/minutes are right.