-
Notifications
You must be signed in to change notification settings - Fork 23
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
panic: send on closed channel using the IndexBatcher #41
Comments
The batcher was contributed by another user, so I don't have much knowledge of the internals. I would start by reviewing this, the line numbers are different, but I believe it's the same panic channel send as this: This suggests the likely cause is that a Batch is being reused incorrectly somehow |
You literally just linked to the same exact issue I found too :) congrats! |
Did a quick review and don't see any obvious problem. It looks like after a batch finishes executing, it is reset and then reused, which should be safe. If you have a sample program that can reproduce it that will help. |
I do actually! It repros very quickly with a load test using hey -- unfortunately the code is not yet published anywhere you can access; privately hosted atm. If you're keen on helping me debug this we can go offline and I can get you access to the code? |
It's not super high priority, but I hate knowing there is an unsolved mystery out there. Let me know what works best for you, you can email me directly at [email protected] |
Thanks! |
I'm trying to use the IndexBatcher in this repo and get a panic:
Not really sure what's triggering this yet... Filing here for visibility.
The text was updated successfully, but these errors were encountered: