Because replace
is a client strategy, it should only remove client locks aka queue locks.
#778
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.
I just tried to use
replace
withuntil_and_while_executing
and noticed, that when I spamTheLockedJob.perform_async(1)
it would replace the job in the queue and also delete the runtime lock of the already running job leading to two jobs running at the same time.The change results in the job correctly being replaced on the queue without removing existing runtime locks for the job.