Fix scanning of files compressed directly via xz (as opposed to tar -J) #650
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.
I've been wondering why scanning
.xz
files does not work and it turns out that there's some nuance with how these files are scanned compared to.tar.xz
files.Files compressed with
xz
can be copied into a file directly viaio.Copy
and using thetar.Reader
will not work;.tar.xz
files (created viatar -J
) will still need to be passed to thetar.Reader
after the xz stream is created.Example:
Original behavior: