[
https://issues.apache.org/jira/browse/COMPRESS-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Desaulniers updated COMPRESS-709:
--------------------------------------
Description:
Continuing the thread started
[here|https://github.com/bazelbuild/bazel/issues/27002].
It looks like [bazel|https://bazel.build/] upgraded commons-compress from 1.20
to 1.26.1 in [their 7.2.0
release|https://github.com/bazelbuild/bazel/pull/22300], and [as of
today|https://github.com/bazelbuild/bazel/blob/b0b5497749eb1550c96d92c52f477689e07dca6f/MODULE.bazel#L241]
are still on that version.
When I upgraded my project from bazel built project from 6.4.0 to 7.6.1 I
experience a build failure during the fetch of one of my compressed tarballs
(attached).
{code:java}
Error in download_and_extract: java.io.IOException: Error extracting
/data/ndesaulniers/CKT22237/.bazel/bazel/e5178882703a799d56ae48491a6f3efc-MyProject/external/tinyxml/temp8022142404010996407/tinyxml.tar.gz
to
/data/ndesaulniers/CKT22237/.bazel/bazel/e5178882703a799d56ae48491a6f3efc-MyProject/external/tinyxml/temp8022142404010996407:
Garbage after a valid .gz stream{code}
FWICT, this only occurs for one of my compressed tarballs; if I remove it, my
build proceeds (including fetching and decompressing other compressed tarballs).
I don't know if this tarball in particular is corrupted, but I am able to
fetch+decompress it with `wget`+`tar`. If I repack it tough, it appears
smaller than the original (perhaps different gzip settings?). I do see the
magic byte pair occurring three times throughout the file. I don't know if it
was created by concatenating three different .gz files together or what; I am
not the creator of the compressed tarball (that we've been using in production
for a few years at this point).
I was not able to find other references in the issue tracker (sorry if this is
a duplicate or already fixed) or commits that may have already fixed this.
If this is a triaged as a bug in compress-commons, then once a fix is
available, we can encourage the bazel user to upgrade their version dependency.
(I probably could have just repacked the compressed tarball and been done with
it, but figured it's worth at least reporting).
was:
Continuing the thread started
[here|https://github.com/bazelbuild/bazel/issues/27002].
It looks like [bazel|https://bazel.build/] upgraded commons-compress from 1.20
to 1.26.1 in [their 7.2.0
release|https://github.com/bazelbuild/bazel/pull/22300].
When I upgraded my project from bazel built project from 6.4.0 to 7.6.1 I
experience a build failure during the fetch of one of my compressed tarballs
(attached).
{code:java}
Error in download_and_extract: java.io.IOException: Error extracting
/data/ndesaulniers/CKT22237/.bazel/bazel/e5178882703a799d56ae48491a6f3efc-MyProject/external/tinyxml/temp8022142404010996407/tinyxml.tar.gz
to
/data/ndesaulniers/CKT22237/.bazel/bazel/e5178882703a799d56ae48491a6f3efc-MyProject/external/tinyxml/temp8022142404010996407:
Garbage after a valid .gz stream{code}
FWICT, this only occurs for one of my compressed tarballs; if I remove it, my
build proceeds (including fetching and decompressing other compressed tarballs).
I don't know if this tarball in particular is corrupted, but I am able to
fetch+decompress it with `wget`+`tar`. If I repack it tough, it appears
smaller than the original (perhaps different gzip settings?). I do see the
magic byte pair occurring three times throughout the file. I don't know if it
was created by concatenating three different .gz files together or what; I am
not the creator of the compressed tarball (that we've been using in production
for a few years at this point).
I was not able to find other references in the issue tracker (sorry if this is
a duplicate or already fixed) or commits that may have already fixed this.
If this is a triaged as a bug in compress-commons, then once a fix is
available, we can encourage the bazel user to upgrade their version dependency.
(I probably could have just repacked the compressed tarball and been done with
it, but figured it's worth at least reporting).
> Unable to decompress compressed tarball: Garbage after a valid .gz stream
> -------------------------------------------------------------------------
>
> Key: COMPRESS-709
> URL: https://issues.apache.org/jira/browse/COMPRESS-709
> Project: Commons Compress
> Issue Type: Bug
> Components: Compressors
> Affects Versions: 1.26.1
> Reporter: Nick Desaulniers
> Priority: Minor
> Attachments: tinyxml.tar.gz
>
>
> Continuing the thread started
> [here|https://github.com/bazelbuild/bazel/issues/27002].
> It looks like [bazel|https://bazel.build/] upgraded commons-compress from
> 1.20 to 1.26.1 in [their 7.2.0
> release|https://github.com/bazelbuild/bazel/pull/22300], and [as of
> today|https://github.com/bazelbuild/bazel/blob/b0b5497749eb1550c96d92c52f477689e07dca6f/MODULE.bazel#L241]
> are still on that version.
> When I upgraded my project from bazel built project from 6.4.0 to 7.6.1 I
> experience a build failure during the fetch of one of my compressed tarballs
> (attached).
> {code:java}
> Error in download_and_extract: java.io.IOException: Error extracting
> /data/ndesaulniers/CKT22237/.bazel/bazel/e5178882703a799d56ae48491a6f3efc-MyProject/external/tinyxml/temp8022142404010996407/tinyxml.tar.gz
> to
> /data/ndesaulniers/CKT22237/.bazel/bazel/e5178882703a799d56ae48491a6f3efc-MyProject/external/tinyxml/temp8022142404010996407:
> Garbage after a valid .gz stream{code}
> FWICT, this only occurs for one of my compressed tarballs; if I remove it, my
> build proceeds (including fetching and decompressing other compressed
> tarballs).
> I don't know if this tarball in particular is corrupted, but I am able to
> fetch+decompress it with `wget`+`tar`. If I repack it tough, it appears
> smaller than the original (perhaps different gzip settings?). I do see the
> magic byte pair occurring three times throughout the file. I don't know if it
> was created by concatenating three different .gz files together or what; I am
> not the creator of the compressed tarball (that we've been using in
> production for a few years at this point).
> I was not able to find other references in the issue tracker (sorry if this
> is a duplicate or already fixed) or commits that may have already fixed this.
> If this is a triaged as a bug in compress-commons, then once a fix is
> available, we can encourage the bazel user to upgrade their version
> dependency.
> (I probably could have just repacked the compressed tarball and been done
> with it, but figured it's worth at least reporting).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
