We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The current implementation breaks if redis is restarted due to broken pipe causing a panic/throw.
Reconnecting with exponential back-off would be extremely helpful, with the new queue in place no work would be lost either.
The text was updated successfully, but these errors were encountered:
This is an interesting idea. I'll have to think more about how this can be implemented. I'd also happily look at PR if someone wants a shot at it.
Sorry, something went wrong.
No branches or pull requests
The current implementation breaks if redis is restarted due to broken pipe causing a panic/throw.
Reconnecting with exponential back-off would be extremely helpful, with the new queue in place no work would be lost either.
The text was updated successfully, but these errors were encountered: