fix end of file handling for gzip files #8386
Merged
Conversation
This file contains hidden or 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
fixes duckdb#8204. The problem is that when the compressed stream ends with a full buffer, it's not really able to detect if the file ended of not. To fix this, I just let the code "wrap around" and with the buffers refreshed, it's a lot easier to check if the file reached its end or not.
|
Thanks for the PR! LGTM |
Closed
1 task
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.
fixes #8204. The problem is that when the compressed stream ends with a full buffer, it's not really able to detect if the file ended of not. To fix this, I just let the code "wrap around" and with the buffers refreshed, it's a lot easier to check if the file reached its end or not.