tower-batch: wake waiting workers on close to avoid hangs #1908
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
After upgrading tower to use tokio
0.3
the tower maintainers noticed they'd introduced a regression where tasks could fail to get woken up when the background task of aBuffer
closed. They've since fixed this regression in tower-rs/tower#480. Well before this change we copiedBuffer
into our codebase as the basis oftower-batch
. Our implementation has this same bug now.Solution
To fix this we just need to apply the same fix they did to our implementation, properly notifying semaphore waiters when we drop or close.
The code in this pull request has:
Review
@teor2345 originally identified this issue
Related Issues
#1805
Follow Up Work