FHIR Chat · Installing to the package cache fails · IG creation

Stream: IG creation

Topic: Installing to the package cache fails


view this post on Zulip Deanne Ukovich (Jun 05 2019 at 22:39):

Our IG is in a constant state of error up on build.fhir.org and I think it may have something to do with the new version of the IG publisher as it has be happening for the last couple of weeks.

It seems to happen when the publisher installs to the local package cache and then tries to read from it. The first read from hl7.fhir.core#3.0.1 works fine, but a subsequent read from hl7.fhir.au.base#current fails

Installing hl7.fhir.au.base#current to the package cache
  Fetching:Publishing Content Failed: null                                                  (31.0415sec)
                                                                                 (31.0415sec)
Use -? to get command line help                                                  (31.0415sec)
                                                                                 (31.0415sec)
Stack Dump (for debugging):                                                      (31.0415sec)
java.lang.NullPointerException
    at java.base/java.io.FilterInputStream.markSupported(FilterInputStream.java:242)
    at org.apache.commons.compress.compressors.gzip.GzipCompressorInputStream.<init>(GzipCompressorInputStream.java:160)

see http://build.fhir.org/ig/aehrc/primary-care-data-technical/build.log for full details

I managed to reproduce this locally with the latest jar by first clearing out the .fhir/packages directory and toggling the auto-ig-builder switch to trigger use of the .fhir/packages directory. It runs fine if it doesn't attempt to use the .fhir/packages directory.

view this post on Zulip Deanne Ukovich (Jun 06 2019 at 23:34):

Some further information, when I reinstated my old .fhir/packages directory locally, I made the error go away. This suggests to me that the fetch of hl7.fhir.au.base#current has worked previously, but is now no longer working for some reason.

view this post on Zulip Jim Steel (Jun 07 2019 at 00:25):

I'm hearing this might be due to AU base moving @Brett Esler

view this post on Zulip Brett Esler (Jun 07 2019 at 01:42):

hi folks - apologies this should have been announced - to reference package-list.json in your project - in your ig.json file set dependencies like
"dependencyList": [
{
"name" : "aubase",
"location" : "http://hl7.org.au/fhir/base",
"version" : "current"
}
],

view this post on Zulip Brett Esler (Jun 07 2019 at 01:43):

for the current build

view this post on Zulip Brett Esler (Jun 07 2019 at 01:43):

or specific version as per http://hl7.org.au/fhir/base/history.shtml

view this post on Zulip Brett Esler (Jun 07 2019 at 01:44):

e.g AU Base 1 release
"dependencyList": [
{
"name" : "aubase",
"location" : "http://hl7.org.au/fhir/base",
"version" : "1.0.2"
}
],

view this post on Zulip Deanne Ukovich (Jun 07 2019 at 02:28):

Thanks Brett, this has resolved the problem above.

view this post on Zulip Brett Esler (Jun 07 2019 at 04:21):

cool - the package-list.json now drives the history view automatically thanks to @Grahame Grieve so can see all of the versioned packages available there

view this post on Zulip Brian Postlethwaite (Jun 07 2019 at 06:47):

Do we need the package id in there too?

view this post on Zulip Brett Esler (Jun 07 2019 at 06:49):

don;t think so if you set location.. @Grahame Grieve what does package id do for us?

view this post on Zulip Grahame Grieve (Jun 07 2019 at 07:48):

package is enough - I convert the canonical location to a package id internally anyway


Last updated: Apr 12 2022 at 19:14 UTC