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
I realize this is 4-5 years old but for anyone that follows.
Items that are added while a batch is executing the callback function due to timer will be silently dropped.
This is because the callback function called by the timer isn't safeguarded by the mutex. To fix
modify the timer handler in the run() func
case <-timer.C: bc.mutex.Lock() defer bc.mutex.Unlock() bc.callback(batch) if bc.input != nil { close(bc.input) bc.input = nil } return
Thanks!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I realize this is 4-5 years old but for anyone that follows.
Items that are added while a batch is executing the callback function due to timer will be silently dropped.
This is because the callback function called by the timer isn't safeguarded by the mutex. To fix
modify the timer handler in the run() func
Thanks!
The text was updated successfully, but these errors were encountered: