Stream: IG creation
Topic: IG Publisher failing for STU3 build
Nick Robison (Oct 30 2019 at 15:34):
Hi folks, this morning our CI builds started failing during our IG generation with the following error coming from the IG publisher:
FHIR IG Publisher Version 0.9.88-SNAPSHOT - Built 2019-10-29T13:38:00.990+11:00 - Git 58db34e37b02
Detected Java version: 11.0.4 from /opt/java/openjdk on amd64 (64bit). 500MB available
Parameters: -ig ig/ig.json
dir = /dpc-app, path = /opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Run time = Wednesday, October 30, 2019 at 3:29:01 PM Greenwich Mean Time (2019-10-30T15:29:01Z)
Package Cache: /root/.fhir/packages (00:00.0028)
Load Configuration from /dpc-app/ig/ig.json (00:00.0039)
Contacting Build Server... (00:00.0051)
... done (00:06.0554)
Root directory: /dpc-app/ig (00:06.0557)
Terminology Cache is at /dpc-app/ig/generated_output/txCache. 0 files in cache (00:06.0569)
Publishing Content Failed: Unable to find the package source for 'hl7.fhir.core#3.0.1' at http://hl7.org/fhir/STU3/package.tgz (00:07.0275)
(00:07.0275)
Use -? to get command line help (00:07.0276)
(00:07.0277)
Stack Dump (for debugging): (00:07.0277)
org.hl7.fhir.exceptions.FHIRException: Unable to find the package source for 'hl7.fhir.core#3.0.1' at http://hl7.org/fhir/STU3/package.tgz
at org.hl7.fhir.utilities.cache.PackageCacheManager.loadPackage(PackageCacheManager.java:629)
at org.hl7.fhir.igtools.publisher.Publisher.loadCorePackage(Publisher.java:2039)
at org.hl7.fhir.igtools.publisher.Publisher.initializeFromJson(Publisher.java:1663)
at org.hl7.fhir.igtools.publisher.Publisher.initialize(Publisher.java:1124)
at org.hl7.fhir.igtools.publisher.Publisher.execute(Publisher.java:611)
at org.hl7.fhir.igtools.publisher.Publisher.main(Publisher.java:6527)
Did the download URL for the STU3 package change? This is with the latest ig publisher, fetched this morning.
Lynn Laakso (Oct 30 2019 at 15:45):
see Technical Corrections thread: https://chat.fhir.org/#narrow/stream/179240-Announcements/topic/Technical.20Corrections
Nick Robison (Oct 30 2019 at 15:48):
Ok. Thank you for the link. I missed the announcements thread.
Shovan Roy (Oct 30 2019 at 22:37):
I'm also facing the same issue since this morning
Sarah Gaunt (Oct 30 2019 at 22:38):
Assuming it's broken for everyone due to the technical corrections - R4 IG build failing too.
Shovan Roy (Oct 30 2019 at 22:40):
Yes, I just noticed that announcement from GG..
Grahame Grieve (Oct 31 2019 at 11:10):
I'm getting close... Will release a new working publisher sometime in the next 24 hours
Grahame Grieve (Oct 31 2019 at 11:10):
one very hard bug in the validator to figure out
Mark Kramer (Nov 08 2019 at 13:58):
Can we keep the stable version of the publisher up while a new candidate is being beta tested? It seems like releasing a fresh build while cutting off access to the pervious one is not good practice.
Lloyd McKenzie (Nov 08 2019 at 16:19):
The publisher is maintained in Maven, so you can always go dig up an old version if you want - it's just easier to grab current. (And as underlying infrastructure changes (e.g. updates to the tx server, changes to core spec & ig packages, etc.), old versions tend to cease working. In theory, the infrastructure should get more stable over time, but evidence suggests we haven't hit that point yet.
Grahame Grieve (Nov 08 2019 at 20:02):
In this case, I rebuilt the infrastructure because of decisions made in committee. Old versions of the publisher (and validator) can no longer function because of their infrastructural dependencies. So there was no 'keep the old version up' (at least, not at the funding point I work with).
Last updated: Apr 12 2022 at 19:14 UTC
