Conversation
…estart The pinned commit of dbader/schedule (1.1.0 era) had a bug in _schedule_next_run: when a timezone was set, it compared self.at_time (in the target TZ, e.g. 20:00 Moscow) against now.time() in local UTC (e.g. 19:35 UTC). Since 20:00 > 19:35, it subtracted 1 day from next_run, landing in the past and causing run_pending() to fire the job immediately on every bot restart. schedule 1.2.1 and 1.2.2 fix this (see dbader/schedule issues #583, #601-604, #623) by using datetime.now(at_time_zone) throughout. Co-Authored-By: Claude Sonnet 4.6 <[email protected]> Claude-Session: https://claude.ai/code/session_01YbEoMDXjYqaE6Vf8g2Cg5S
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
1 participant
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.
…estart
The pinned commit of dbader/schedule (1.1.0 era) had a bug in _schedule_next_run: when a timezone was set, it compared self.at_time (in the target TZ, e.g. 20:00 Moscow) against now.time() in local UTC (e.g. 19:35 UTC). Since 20:00 > 19:35, it subtracted 1 day from next_run, landing in the past and causing run_pending() to fire the job immediately on every bot restart.
schedule 1.2.1 and 1.2.2 fix this (see dbader/schedule issues #583, #601-604, #623) by using datetime.now(at_time_zone) throughout.
Claude-Session: https://claude.ai/code/session_01YbEoMDXjYqaE6Vf8g2Cg5S