Don’t set delayUntil
if there is no delay
#140
Merged
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.
These changes are now available in 1.17.1
Currently, if a job is retried with no delay, the
delayUntil
property is set to the current time. I noticed this since it was causing some issues with a new test in vapor-community/vapor-queues-fluent-driver#15. This PR adjusts this so thatdelayUntil
isnil
when there is no retry delay. This aligns the behaviour with how new jobs with no delay are created.