You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
HAPPlatformTimerRegister specifies duration to be an absolute deadline value, relative to HAPPlatformClockGetCurrent
however, it is sometimes also invoked with 0, which i take it means "ASAP" (1, 2).
this is not documented in API and may trigger bugs in implementations.
The text was updated successfully, but these errors were encountered:
rojer
added a commit
to mongoose-os-libs/homekit-adk
that referenced
this issue
Apr 10, 2021
Turns out, HAPPlatformTimerRegister may be invoked with deadline of 0 sometimes.
This translates into a negative duration for mgos_set_timer, which is fine
for the first 24.85 days but then duration rolls over and things go south.
Instead, clamp negative duration to 0 while it's still a 64-bit int.
apple/HomeKitADK#102Fixesmongoose-os-apps/shelly-homekit#129
HAPPlatformTimerRegister specifies duration to be an absolute deadline value, relative to HAPPlatformClockGetCurrent
however, it is sometimes also invoked with 0, which i take it means "ASAP" (1, 2).
this is not documented in API and may trigger bugs in implementations.
The text was updated successfully, but these errors were encountered: