FHIR Chat · Input is not in the .gz format · IG creation

Stream: IG creation

Topic: Input is not in the .gz format


view this post on Zulip Bryn Rhodes (Feb 20 2020 at 16:38):

Getting this error on the QI-Core continuous build, as well as locally. I've pulled the latest publisher and cleared my local cache, but still get this same error. Anyone else seeing this?

view this post on Zulip Bryn Rhodes (Feb 20 2020 at 16:38):

java.io.IOException: Input is not in the .gz format
        at org.apache.commons.compress.compressors.gzip.GzipCompressorInputStream.init(GzipCompressorInputStream.java:193)
        at org.apache.commons.compress.compressors.gzip.GzipCompressorInputStream.<init>(GzipCompressorInputStream.java:167)
        at org.apache.commons.compress.compressors.gzip.GzipCompressorInputStream.<init>(GzipCompressorInputStream.java:131)
        at org.hl7.fhir.utilities.cache.NpmPackage.readStream(NpmPackage.java:274)
        at org.hl7.fhir.utilities.cache.NpmPackage.fromPackage(NpmPackage.java:269)
        at org.hl7.fhir.utilities.cache.PackageCacheManager.addPackageToCache(PackageCacheManager.java:431)
        at org.hl7.fhir.utilities.cache.PackageCacheManager.loadPackage(PackageCacheManager.java:576)
        at org.hl7.fhir.igtools.publisher.Publisher.resolveDependency(Publisher.java:2455)
        at org.hl7.fhir.igtools.publisher.Publisher.loadIg(Publisher.java:2414)
        at org.hl7.fhir.igtools.publisher.Publisher.initializeFromJson(Publisher.java:1861)
        at org.hl7.fhir.igtools.publisher.Publisher.initialize(Publisher.java:1210)
        at org.hl7.fhir.igtools.publisher.Publisher.execute(Publisher.java:661)
        at org.hl7.fhir.igtools.publisher.Publisher.main(Publisher.java:6934)

view this post on Zulip Grahame Grieve (Feb 20 2020 at 20:25):

I bet it's your http cache

view this post on Zulip Grahame Grieve (Feb 20 2020 at 20:25):

hm no- the ci build too? I'll investigate

view this post on Zulip Bryn Rhodes (Feb 21 2020 at 18:35):

So I even tried going back to the previous version of the publisher that used to work, and it's getting the same error. Seems to happen when it tries to unpack the US Core package.

view this post on Zulip Bryn Rhodes (Feb 21 2020 at 19:25):

So, going back to 1.0.37-SNAPSHOT I can successfully build locally.

view this post on Zulip Grahame Grieve (Feb 21 2020 at 19:35):

it works for me with current code, and on the ci-build?

view this post on Zulip Bryn Rhodes (Feb 21 2020 at 20:05):

I just kicked the ci-build and got the same error, and running 1.0.65-SNAPSHOT locally I get the error.

view this post on Zulip Grahame Grieve (Feb 21 2020 at 20:08):

@Josh Mandel this build Bryn is talking about failed: http://build.fhir.org/ig/HL7/fhir-qi-core/branches/master/failure/build.log. But https://fhir.github.io/auto-ig-builder/builds.html still shows it as successful?

view this post on Zulip Grahame Grieve (Feb 21 2020 at 20:09):

@Bryn Rhodes the log shows something weird:

view this post on Zulip Grahame Grieve (Feb 21 2020 at 20:10):

Installing hl7.fhir.us.core.r4validator#3.1.0 to the package cache
  Fetching:Publishing Content Failed: Input is not in the .gz format                        (00:18.0824)

view this post on Zulip Grahame Grieve (Feb 21 2020 at 20:10):

my local log shows something different:

view this post on Zulip Grahame Grieve (Feb 21 2020 at 20:10):

Installing hl7.fhir.us.core#3.1.0 to the package cache

view this post on Zulip Grahame Grieve (Feb 21 2020 at 20:10):

what do you get locally?

view this post on Zulip Josh Mandel (Feb 21 2020 at 20:20):

But https://fhir.github.io/auto-ig-builder/builds.html still shows it as successful?

Thanks -- jush pushed a fix for this. (The successful run's qa was taking precedence when it shouldn't have.)

view this post on Zulip Bryn Rhodes (Feb 21 2020 at 20:52):

Yeah, my local build shows the same as the CI build:

Load Package hl7.fhir.xver-extensions#0.0.1
Installing hl7.fhir.us.core.r4validator#3.1.0 to the package cache
  Fetching:Publishing Content Failed: Input is not in the .gz format

view this post on Zulip Grahame Grieve (Feb 21 2020 at 20:55):

I don't understand this at all

view this post on Zulip Bryn Rhodes (Feb 21 2020 at 21:01):

Yeah, it's definitely strange. I thought it might be some strange characters in the dependencylist, so I removed that, built, got the expected error about missing US Core required dependencies, then re-keyed the dependency manually in the ig.json and got the same error.

view this post on Zulip Grahame Grieve (Feb 21 2020 at 21:03):

It's something in the package subsystem but I can't think why I can't reproduce it

view this post on Zulip Bryn Rhodes (Feb 21 2020 at 21:44):

Just had a mac user try it and he's getting the same error as well, same log output (hl7.fhir.us.core.r4validator#3.1.0).

view this post on Zulip Bryn Rhodes (Feb 21 2020 at 22:29):

Whatever you did with 1.0.66 fixed it. Thanks Grahame!

view this post on Zulip Grahame Grieve (Feb 21 2020 at 22:30):

interesting. I did not expect that to fix it

view this post on Zulip Eric Haas (Mar 24 2020 at 23:41):

i am getting this error now to when I try to load the latest QI Core.

Installing hl7.fhir.us.qicore#4.0.0 to the package cache
  Fetching:Publishing Content Failed: Input is not in the .gz format                        (00:35.0874)

view this post on Zulip Eric Haas (Mar 24 2020 at 23:42):

was there ever a fix for this?

view this post on Zulip Eric Haas (Mar 24 2020 at 23:43):

as a workaround I manually loaded the package locally.

view this post on Zulip Eric Haas (Mar 25 2020 at 01:43):

also now on my local build the qicore links all resolve to: about:blank#blocked

view this post on Zulip Eric Haas (Mar 27 2020 at 19:28):

the autobuilder is also failing with the following error for the DEQM CI Build with the dependency to the newly published QI Core 4.0.0.

Installing hl7.fhir.us.qicore#4.0.0 to the package cache
  Fetching:Publishing Content Failed: Input is not in the .gz format                        (00:19.0340)

view this post on Zulip Grahame Grieve (Mar 29 2020 at 21:17):

fixed next release


Last updated: Apr 12 2022 at 19:14 UTC