Fix schedule hooks firing when timestamp <= now #817
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.
When
enqueue_atis called with a timestamp in the past or equal to now, the job bypasses the delayed queue and goes directly to the work queue. Previously,before_scheduleandafter_schedulehooks were incorrectly called in this case.This fix moves
process_schedule_hooksinside theelsebranch so hooks only fire when jobs actually enter the delayed queue.Fixes #816