-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
[8.x] Enexpected withChain(...)
behaviour
#35041
Labels
Comments
Looks like the problem lays here: framework/src/Illuminate/Foundation/Bus/PendingChain.php Lines 136 to 153 in 363dc94
Here we are force-overriding the queue even if it was not specified (like here: $firstJob->allOnConnection($this->connection);
$firstJob->allOnQueue($this->queue); Should we do something like that? if ($this->connection !== null) {
$firstJob->allOnConnection($this->connection);
}
if ($this->queue !== null) {
$firstJob->allOnQueue($this->queue);
} |
Opened #35047 with a fix |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8.12.3
7.4.11
mysql Ver 8.0.19 for macos10.15 on x86_64 (MySQL Community Server - GPL)
Description:
There are 3 classes:
Base job
JobHigh
that should be processed in thehigh
queueJobMedium
that should be processed in themedium
queueWhile in Laravel 7 (
7.28.4
) bothdispatch(new JobHigh); dispatch(new JobMedium);
andJobHigh::withChain(new JobMedium)->dispatch()
throw jobs to the appropriate queues, in Laravel 8 (8.12.3
) that's not a case forwithChain(...)
.Is that a bug? Or that's a change that was accidentally not included
Upgrade Guide
.Steps To Reproduce:
Laravel 7:
Laravel 8:
Laravel 7:
Laravel 8:
The text was updated successfully, but these errors were encountered: