Fix cache warming schedule again #2508
Merged
Conversation
This file contains 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
It turns out that Whenever does something weird when you provide a minutes argument that is less than or equal to 30. It assumes you mean 'every n minutes' whereas for values greater than 30, if assumes you mean 'the nth minute'. [Whenever specs describing the behaviour](https://github.com/javan/whenever/blob/e916b58f29ea4da76de9ddc5aca8c85a5f29f897/test/unit/cron_test.rb#L17-L19) So, when the random number generates an 8, whenever generates a schedule like this (edited for brevity): > 8,16,24,32,40,48,56 * * * * /bin/bash -l -c 'rake registries:cache_refresh' We'll switch to using raw cron syntax instead. [From the Readme](https://github.com/javan/whenever/blob/e916b58f29ea4da76de9ddc5aca8c85a5f29f897/README.md): > every '0 0 27-31 * *' do > command "echo 'you can use raw cron syntax too'" > end
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.
It turns out that Whenever does something weird when you provide a minutes argument that is less than or equal to 30. It assumes you mean 'every n minutes' whereas for values greater than 30, it assumes you mean 'the nth minute'.
Whenever specs describing the behaviour
So, when the random number generates an 8, whenever generates a schedule like this (edited for brevity):
We'll switch to using raw cron syntax instead. From the Readme: