Repository navigation
fix: schedule in local time with cron's DST fix - #2
Merged
Merged
Conversation
Go back to scheduling in the system's local time and use cron from git at cf2dc1d5, which includes zslayton/cron#145. The released 0.16.0 and 0.17.0 can hang when the clocks go back. Switch back to a crates.io release once one includes the fix.
ab-ioannis
added a commit
to AngryBytes/docker-images
that referenced
this pull request
Oct 26, 2026
Pin pocketcron to sha256:d3c0dc1abbff683809a694ea7df80adcfd87e1ed6545795dc3ae6d554966cae2, which schedules in the system's local time again and uses cron's unreleased fix for the hang when the clocks go back (AngryBytes/pocketcron#2).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changelog
cronfrom git atcf2dc1d5, which includes Fix folded time zslayton/cron#145 ("Fix folded time"). That fix isn't in a crates.io release yet, so switch back to a release once one includes it.--lockedimage build from fix: schedule in utc #1.Why
With
cron0.16.0 (and 0.17.0), pocketcron can hang at 100% CPU when the clocks go back, on systems in a time zone with daylight saving time. #1 avoided that by scheduling in UTC, but that changes what crontab times mean on those systems. With the fix from zslayton/cron#145, local-time schedules no longer hang.Testing
cargo build --locked,cargo fmt --checkandcargo clippyare all clean.TZ=Europe/Amsterdamacross 2026-10-25, 2027-03-28 and 2027-10-31 using thiscroncommit: no hang, and a0 0 * * *job ran at 00:00 local time every day.crondoesn't change it.cronfrom git) and checked withTZ=Asia/Kolkatathat jobs follow local time.