[11.x] Fixed pop on default Beankstalkd queue when not specifically added #51759
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.
This pull request addresses a change in behavior observed when migrating from Laravel 10 to Laravel 11. The pop method in the queue implementation has been enhanced to ensure that it only watches the specified queue and ignores any previously watched queues, effectively restoring the behavior from Laravel 10.
Problem Statement
In Laravel 11, when launching a worker on a specific queue using the artisan command php artisan queue:work --queue=one, the worker listens to both the specified queue (one) and the default queue of Beanstalkd. This results in the worker popping jobs from both queues, which can lead to unintended job processing and potential job loss from queues meant to be handled by separate workers.