-
Notifications
You must be signed in to change notification settings - Fork 11
Custom Queues config #17
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
base: master
Are you sure you want to change the base?
Conversation
446860a to
d9abe70
Compare
|
Fixed tests |
e8fa611 to
8731cb9
Compare
|
updated readme |
8731cb9 to
7b95282
Compare
…entry errors updated readme improved error handling with queues
7b95282 to
5ae35ae
Compare
|
Great thanks! I'll try to find some time over the next couple of days to review & merge. |
|
Also improves error handling with queue jobs. |
|
Improving the error handling would be much welcome, as currently I sometimes find Beanstalkd crashed because it accumulated 70K tasks of exceptions that can't be sent to Sentry and thus get into a loop of trying to send exception, fails so throws exception, which it tries to send to Sentry, which fails and thus generates a new exception, which it tries to send to Sentry, which fails... ad aeternum, or until Beanstalkd keels over. |
|
Any word on this? |
|
Any news on this? |
Added ability to specify the queue connection and the actual queue to write errors to via config