fix: change start_time source in CronTrigger.next_fire() #1718
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.
Pull Request Type
Description
Changes the source of start_time in
CronTrigger.next_fire()
to fix a bug causing possible multiple firing.This fix ensures that the next firing time of the task trigger would always advance after the task is fired. Before the fix, it is possible for the next fire to not advance, due to using
datetime.now()
for the reference start time and the possibility that the task fires just moments before the supposed start time. See attached issue for illustration.Changes
CronTrigger.next_fire()
fromdatetime.now()
toself.last_call_time
.Related Issues
#1717
Test Scenarios
The following creates a cron-triggered task every minute to print the current time to standard output.
Example output before fix:
Example output after fix:
Python Compatibility
3.10.x
3.11.x
Checklist
pre-commit
code linter over all edited files