Bug 15541 – RTC alarm timer for next alarm does not get set when rtc alarm is in progress and server returns

Bug 15541 - RTC alarm timer for next alarm does not get set when rtc alarm is in progress and server returns

Summary:

RTC alarm timer for next alarm does not get set when rtc alarm is in progress...

Status:	NEW

Product:	SqueezePlay
Classification:	Unclassified
Component:	Applet
Version:	7.4.x
Platform:	PC Other

Importance:	P3 normal with 1 vote (vote)
Target Milestone:	Future
Assigned To:	Ben Klaas

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-01-26 15:05 UTC by Ben Klaas
Modified:	2011-01-14 09:41 UTC (History)
CC List:	2 users (show)

See Also:
Category:	Bug

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ben Klaas 2010-01-26 15:05:05 UTC

If a client-side fallback occurs

and

Server reconnects during fallback alarm (either when active or in snooze), and there is an alarm scheduled behind the fallback (e.g., tomorrow's alarm at the same time)

the playerAlarmState notification will fail to start a fallback timer because self.alarmInProgress == 'rtc' and we are coded to not reset the timer to the server-configured alarm time in that situation

if the next alarm time hits and the server is down at this time as well, the alarm will not sound.

Comment 1 Ben Klaas 2010-02-12 04:37:47 UTC

realistically, this probably won't be looked at until after 7.5.0 release. That release is focused on SB Touch

Comment 2 Chris Owens 2010-03-08 11:33:02 UTC

Moving lower-priority bugs to next target

Comment 3 Ben Klaas 2011-01-14 09:41:52 UTC

this bug is a microcosm of how horrible it is to sanely code a server-driven alarm with client-side fallbacks, esp. when the server communication about configured alarms is imperfect. welcome to my hell.

target to future