Flush is broken when ordering enabled and multiple batches present #1702
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.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #<issue_number_goes_here> 🦕
Note: If you are opening a pull request against a
legacy
branch, PLEASE BE AWARE that we generally won't accept these except for things like important security fixes, and only for a limited time.flush
is currently broken when you have ordering + multiple batches when the flush occurs, aspublishDrain
gets called with a callback that's dropped in thepublish
implementation ofOrderedQueue
. The callback is not passed on tobeginNextPublish
, so the flush will never complete as it's waiting for the callback to be called. Looks like this came in with #1691.Haven't looked into tests etc. Let me know what you think makes sense, if this is interesting to merge.