Add support for job delay in CloudTasksQueue #184
Merged
+73
−1
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.
Fix: Pass job delay to pushRaw in push method
Problem
When dispatching jobs using the
push()method, the delay property from the job object was not being passed topushRaw(). This meant that jobs with a configured delay would be executed immediately instead of being scheduled for the specified time.Solution
Updated the
push()method to extract thedelayproperty from the job object (if present) and include it in the options array passed topushRaw(). This ensures that delayed jobs are properly scheduled with their intended execution time.The implementation now:
delaypropertyrelease()method which already follows this patternChanges
src/CloudTasksQueue.phplines 135-142pushRaw()This brings the
push()method in line with how delays are handled in therelease()method, ensuring consistent behavior across the queue system.