-
Notifications
You must be signed in to change notification settings - Fork 11.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[5.7] When scheduling a job, respect the already set queue #25216
[5.7] When scheduling a job, respect the already set queue #25216
Conversation
@@ -97,6 +97,7 @@ public function job($job, $queue = null, $connection = null) | |||
$job = is_string($job) ? resolve($job) : $job; | |||
|
|||
if ($job instanceof ShouldQueue) { | |||
$queue = $queue ?? $job->queue; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason why you don't also consider the job connection?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just resubmitted #25159 so that it gets merged ASAP before 5.7 gets released which is basically any day now, so I didn't even consider the connection. But you are right, the connection should also be respected so I updated the PR accordingly.
b532761
to
5841a92
Compare
5841a92
to
a3749b1
Compare
I found I had to explicitly set the connection for my SQS queues to work. SQS would receive the message but it would continuously retry to process until it went into the dead letter queue. This failed to process even though my default connection was 'sqs'.
while this worked
Controller
Job LoadManifestFile
config/queue.php
|
I am having the same issue with redis, it only dispatches to redis if I specify ->onConnection('redis'). |
Resubmit of #25159 with a proper test.