-
-
Notifications
You must be signed in to change notification settings - Fork 198
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
Data race in consumer #36
Comments
Interesting, thank you. I see that this can be triggered if two I forgot about the fact that the function could run multiple times concurrently. :( There's a few ways to go about guard running that segment of code. I'll have a fix out imminently once I figure out which approach I like best. |
Pushed a fix, I'll tag a release likely later today. Just out of curiosity, what were the conditions that triggered this? I mention one scenario in my commit message, but the more likely scenario I think is that the first few |
Tag likely tomorrow actually, I'm close to finishing the documentation I've been trying to finish for a few weeks now. |
Just stress tested an application that uses the library. Use case is normal consumption loop with |
The tag took a but, but 0.7.0 is now released that contains this bugfix. |
Version:
0.6.14
The text was updated successfully, but these errors were encountered: