Fix logging messages after flush() #7
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We need to reset the "flushed" flag on each write() invocation. Otherwise we would buffer data and never flush it out as demonstrated in max-heller#4 (comment) Add unit test for this corner case.
thomasjfox
force-pushed
the
fix-write-after-flush
branch
from
ec7b14a to
6dd0a2c
Compare
max-heller
approved these changes
May 4, 2024
|
Released in v0.3.1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We need to reset the "flushed" flag on each write() invocation. Otherwise we would buffer data and never flush it out as demonstrated in #4 (comment)
Add unit test for this corner case.