Comment 17 for bug 633352

Hmmm. Just noticed something. Not sure if it's relevant or not as I don't yet understand how the code works:

[calAlarmService] considering alarm for item: Update: TIGER ONLY: SDN Post Mortem and Workout alarm time: 2010/11/15 21:15:00 UTC isDate=0 snooze time: 2010/11/15 21:15:00 UTC isDate=0
[calAlarmService] now is 2010/12/07 23:44:49 UTC isDate=0
[calAlarmService] last ack was: 2010/11/15 21:14:59 UTC isDate=0
[calAlarmService] alarm is in the past and unack'd, firing now!

[calAlarmService] considering alarm for item: Tiger Thanksgiving alarm time: 2010/11/19 18:45:00 UTC isDate=0 snooze time: 2010/11/19 18:45:00 UTC isDate=0
[calAlarmService] now is 2010/12/07 23:44:49 UTC isDate=0
[calAlarmService] last ack was: 2010/11/19 18:44:59 UTC isDate=0
[calAlarmService] alarm is in the past and unack'd, firing now!

Notice that for both events, the "last ack" time is 1 second before the alarm time and snooze time. That seems a little odd, no?

I also noticed that all my other events are not like this. For my other events, the "last ack" time is typically hours after the alarm time. Also my other events have "snooze time: null" so I'm not sure if snoozing the alarms has something to do with this bug or not.