Fixed double-writes when write() is called during 'drain' event #22
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.
When
write()is called in the event handler of adrainevent,Buffercan write things twice.Example:
This write
"foo\nfoo\nbar\n"instead of just"foo\nbar\n".This doesn't happen if
$buffer->write("bar\n");is called on the next tick (which explains why it usually works).This happens in actual code, e.g. when using
Util::pipe()on a Readable which immediately emits a'data'event whenresume()is called.This PR fixes this by updating the internal buffer before emitting the
drainevent.