write::BzDecoder: Fix infinite loop on drop when no data is read or written #118
+9
−1
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.
If writes to the
BzDecoder
end before it has been fed the entire stream and the output buffer has already been flushed to the wrapped writer, then theDrop
implementation will loop forever. On drop,try_finish()
is called, which repeatedly tries towrite()
untilBZ_STREAM_END
is returned or an error occurs, but neither scenario happens if there's no input nor output data to process.This commit makes
try_finish()
return anUnexpectedEof
error in this scenario.(Also, really happy to see this library found a new maintainer!)