Skip to content
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

Custom Queues config #17

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

pulkitjalan
Copy link

Added ability to specify the queue connection and the actual queue to write errors to via config

'queue' => [
        /*
        |--------------------------------------------------------------------------
        | Connection
        |--------------------------------------------------------------------------
        |
        | Set the connection to use from the list in config/queue.php
        |
        */
        'connection' => '',

        /*
        |--------------------------------------------------------------------------
        | Queue
        |--------------------------------------------------------------------------
        |
        | Set the queue to use for raven
        |
        */
        'queue' => ''
   ]

@pulkitjalan
Copy link
Author

Fixed tests

@pulkitjalan pulkitjalan force-pushed the customQueues branch 3 times, most recently from e8fa611 to 8731cb9 Compare August 21, 2014 08:34
@pulkitjalan
Copy link
Author

updated readme

…entry errors

updated readme
improved error handling with queues
@rcrowe
Copy link
Owner

rcrowe commented Sep 22, 2014

Great thanks! I'll try to find some time over the next couple of days to review & merge.

@pulkitjalan
Copy link
Author

Also improves error handling with queue jobs.

@borfast
Copy link

borfast commented Sep 22, 2014

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.

@tomschlick
Copy link

Any word on this?

@pulkitjalan
Copy link
Author

Any news on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants