-
Notifications
You must be signed in to change notification settings - Fork 422
allow laravel to end workers with lost connection - laravel 8 and php ^7.3 #576
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
Comments
PR is merged in maintained versions. |
It does not work for me. Running 13.3.5 on Laravel 10.46.0. I had to kill the container (worker) manually. Am I missing some setting? Or is it issue with tries? I run workers like this: php /app/artisan queue:work --queue=generate --tries=10 --memory=10000 --timeout=180 rabbitmq
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
worker not being stopped after rbmq connection lost
connected issue:
457
fix is included in package version 12.0.1 which needs php version 8, but is currently not an option for me.
Steps To Reproduce
./artisan queue:work
Current behavior
worker not being stopped after rbmq connection lost
Expected behavior
worker should be stopped.
Fix
can you add PR 457 fix also to package version 11.* as an fix version 11.3.1. Then I can update my laravel project withoud my own workarounds
The text was updated successfully, but these errors were encountered: