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
"Job received" Event #124
Comments
That's a great idea and it's easy to implement. I'll do it this weekend! |
Now that is service! Thank you so much. |
Sorry for the delay! It took me some time last weekend to realize that it was better to make this feature local to a limiter inside a Cluster. Once I realized that, it didn't take much time to implement. Bottleneck 2.19.0 adds the following events: For your use case, you would use either
Please let me know how it works for you! |
Thank you Simon! I think others will find this very useful too where a bottleneck instance can be accessed from lots of different points in the code. |
I agree, it's such an obvious feature in retrospect that I'm surprised I didn't think about it and no one suggested it earlier. |
Would be great to have an event that fired when a job is received by the bottleneck. Our code is sending to a single instance of a bottleneck from a large variety of places and modules which makes this hard to track.
If there is an existing way to do this then please let me know!
The text was updated successfully, but these errors were encountered: