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
I'm using a default Scheduler to trigger jobs at regular intervals, pretty standard, but when the timezone says it's time to move into winter time, aka when the clock moves back an hour, this happens:
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', .cargo/registry/src/index.crates.io-6f17d22bba15001f/clokwerk-0.4.0/src/intervals.rs:214:41
And it will repeat this error on every restart for the next hour until the "repeated hour" has passed. After that, everything's back to working like normal.
For interval-only use cases I can likely work around this by settings the Scheduler's timezone to UTC, but that of course won't work for everyone.
Thanks for the otherwise great scheduler lib, btw.
The text was updated successfully, but these errors were encountered:
codifryed
added a commit
to codifryed/coolercontrol
that referenced
this issue
Apr 12, 2024
Workaround for upstream issue (mdsherry/clokwerk#38), where going back in time (DST end) caused panic.
For our current use cases using UTC is fine. That may not be the case if we should ever implement time-based triggers.
Hi there,
I'm using a default Scheduler to trigger jobs at regular intervals, pretty standard, but when the timezone says it's time to move into winter time, aka when the clock moves back an hour, this happens:
And it will repeat this error on every restart for the next hour until the "repeated hour" has passed. After that, everything's back to working like normal.
For interval-only use cases I can likely work around this by settings the Scheduler's timezone to UTC, but that of course won't work for everyone.
Thanks for the otherwise great scheduler lib, btw.
The text was updated successfully, but these errors were encountered: