FHIR Chat · Breaking Change to IG publisher · IG creation

Stream: IG creation

Topic: Breaking Change to IG publisher


view this post on Zulip Grahame Grieve (Sep 01 2021 at 06:27):

I am just releasing a new IG publisher. This IG publisher includes a breaking change, and it may impact on you.

The change is that by default, when you nominate a template in ig.ini, if you don't nominate a version, like this:

[IG]
ig = input/hl7-fhir-us-ecr.xml
template = hl7.fhir.template

Then the IG publisher will default to the most recent published version, not the current ci-build version. It's been doing that - using the ci-build version - but that is not what is documented to happen, and it doesn't make sense. So from now on, it will default to the most recent published version. If you want to opt in to the ci-build version of the template, do this:

[IG]
ig = input/hl7-fhir-us-ecr.xml
template = hl7.fhir.template#current

In practice, the most recent published version of the template is the same as the ci-build for the common templates, and you won't notice the change from ci-build to last release.

But you will notice this if the template has never been formally released. If it hasn't, and you don't explicitly nominate the current version, the build will fail since there is no released version. You can resolve this one of two ways:

  • nominate the current version as shown above.
  • ask me to release the template into the packaging system

(or both!)

view this post on Zulip Jose Costa Teixeira (Sep 01 2021 at 06:51):

technical question: does it ALWAYS download the ci-build version, or it still uses the data in the package.json to see if it has to download it?

view this post on Zulip Grahame Grieve (Sep 01 2021 at 06:53):

it checks the date and compares them

view this post on Zulip Antonia Schmidt (Sep 01 2021 at 08:52):

I run into issues using the newest verison of the IG publisher: "Error performing operation 'validate-code: null' (parameters = "") for "http://loinc.org#...".

view this post on Zulip Grahame Grieve (Sep 01 2021 at 09:24):

how to reproduce that?

view this post on Zulip Antonia Schmidt (Sep 01 2021 at 09:52):

Terminology Server Log says "POST http://tx.fhir.org/r4/CodeSystem/$validate-code? HTTP/1.0". Looks like the parameters, in this case the loin codes, got lost somewhere.

view this post on Zulip Jose Costa Teixeira (Sep 01 2021 at 10:25):

@Antonia Schmidt can you point to a repository or somehow provide what you could do with the previous version of the publisher but is no longer working?

view this post on Zulip Grahame Grieve (Sep 01 2021 at 11:15):

in the body, not the URL

view this post on Zulip David deRoode (Sep 01 2021 at 14:26):

Same new errors on Dental (https://build.fhir.org/ig/HL7/dental-data-exchange/branches/master/qa.html)

view this post on Zulip Grahame Grieve (Sep 01 2021 at 19:18):

which ones are new?

view this post on Zulip Grahame Grieve (Sep 01 2021 at 20:29):

a new version coming out sooon

view this post on Zulip Corey Spears (Sep 02 2021 at 06:36):

Still seeing this error. Seems to be affecting all IGs building with terminologies.

view this post on Zulip Grahame Grieve (Sep 02 2021 at 07:12):

I haven't got a new version out yet

view this post on Zulip Grahame Grieve (Sep 02 2021 at 07:12):

fighting with the build system

view this post on Zulip Rob Hausam (Sep 02 2021 at 20:20):

I've been seeing the same "Error performing operation 'validate-code: null' (parameters = "") for "http://loinc.org#..." issues, too. At this moment these issues are being hidden by another publisher issue that I'm trying to get fixed, but before that I had over 120 of them. @Grahame Grieve

view this post on Zulip Grahame Grieve (Sep 02 2021 at 20:25):

you shouldn't see them now

view this post on Zulip Rob Hausam (Sep 02 2021 at 21:23):

I still have 37 of these errors for LOINC in the CI build that just completed. @Grahame Grieve

view this post on Zulip Grahame Grieve (Sep 02 2021 at 22:09):

have you cleared txCache?

view this post on Zulip Rob Hausam (Sep 02 2021 at 23:16):

Just replied on the other topic - probably not yet since you fixed this.


Last updated: Apr 12 2022 at 19:14 UTC