FHIR Chat · IG other package references · IG creation

Stream: IG creation

Topic: IG other package references

Brett Esler (Jun 08 2018 at 01:56):

@Grahame Grieve I am attempting to build http://build.fhir.org/ig/hl7au/au-fhir-pd which references au-fhir-base

"dependencyList": [
    {
       "name" : "aubase",
       "location" : "http://hl7.org.au/fhir",
       "version" : "current"
    }
  ],

in my ig.json file
package list is resolved at http://hl7.org.au/fhir/package-list.json
build seems to work fine
when I look in the PD IG .e.g http://build.fhir.org/ig/hl7au/au-fhir-pd/StructureDefinition-au-pd-practitionerrole.html
the extensions in AU base are not resolved - just getting the canonical url e.g. http://hl7.org.au/fhir/StructureDefinition/meta-source and http://hl7.org.au/fhir/StructureDefinition-au-assigningauthority.html
these are available e.g. http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-meta-source.html which is where I thought the PD IG output would point due to the dependency load above; and the package-list referencing http://build.fhir.org/ig/hl7au/au-fhir-base
Is this a problem or have I got something wrong?

Grahame Grieve (Jul 06 2018 at 20:48):

your location looks wrong to me - why are you claiming the location of http://hl7.org.au/fhir?

Brett Esler (Jul 17 2018 at 23:13):

location is where the package-list.json is http://hl7.org.au/fhir/package-list.json - CI build entry is
{
"version": "current",
"date": "n/a",
"desc": "Continuous Integration Build (latest in version control)",
"path": "http://build.fhir.org/ig/hl7au/au-fhir-base",
"status": "ci-build"
},

Brett Esler (Jul 17 2018 at 23:15):

IG builder locates the reference ok but all links point at http://hl7.org.au/fhir rather than http://build.fhir.org/ig/hl7au/au-fhir-base

Brett Esler (Jul 17 2018 at 23:16):

should location be http://build.fhir.org/ig/hl7au/au-fhir-base ? how to resolve package-list.json?

Bryn Rhodes (Jul 19 2018 at 20:46):

I'm running into a similar issue with an IG; not sure if it's the same issue, but I've added a package-list to QI-Core, but it's only in the CI build, and when I point the dependency there using the location, I get a canonical mismatch. But I can't put the package-list on the HL7 site where the canonical will match (because it's not published yet). How do I reference an unpublished IG as a dependency?

Eric Haas (Jul 19 2018 at 20:54):

use [package-name]-dev

Eric Haas (Jul 19 2018 at 20:55):

e.g., hl7.fhir.smart-dev

Bryn Rhodes (Jul 19 2018 at 21:40):

Like this:
"dependencyList": [
{
"name": "qicore-dev",
"location": "http://hl7.org/fhir/us/qicore",
"version": "3.0.1",
"source": "lib/qicore"
}
],

Bryn Rhodes (Jul 19 2018 at 21:41):

When I do that I get "package name must be a valid token: 'qicore-dev'"

Eric Haas (Jul 19 2018 at 22:06):

is it in your directory?

Bryn Rhodes (Jul 19 2018 at 22:12):

In lib/qicore, yes

Christopher Schuler (Jul 19 2018 at 22:13):

Should it be hl7.fhir.us.qicore-dev?

Bryn Rhodes (Jul 19 2018 at 22:18):

Here's the one from qicore though:

"dependencyList": [
    {
      "name": "uscore",
      "location": "http://hl7.org/fhir/us/core",
      "version": "1.0.1",
      "source": "lib/uscore"
    }
  ],

Eric Haas (Jul 19 2018 at 22:23):

I'm building us-core locally so I can send an example

Christopher Schuler (Jul 19 2018 at 22:24):

Hmm. Well http://hl7.org/fhir/us/qicore/package-list.json results in a 404. Whereas http://hl7.org/fhir/us/core/package-list.json has several packages.

Bryn Rhodes (Jul 19 2018 at 22:26):

Right, and I've created the package-list for qi-core, and put it in the current build, but until it gets published, it won't actually be available at the canonical url.

Bryn Rhodes (Jul 19 2018 at 22:26):

Which would be true in general of any IG, so wondering how we would support declaring a dependency on an IG that isn't yet published.

Grahame Grieve (Jul 19 2018 at 22:28):

so package resolution is basically broken right now until we can get a package server up. but that's not going to happen in the near term. So the resolution process goes like this:

• look in the local package cache (and anything you build locally will be in there)
• look on build.fhir.org current build package list
• look for package-list.json at the canonical URL

Grahame Grieve (Jul 19 2018 at 22:28):

I can upload the package-list manually now.

Grahame Grieve (Jul 19 2018 at 22:28):

but you should not need that.

Grahame Grieve (Jul 19 2018 at 22:28):

you should actually specify the package properly as your dependency and then it should resolve

Eric Haas (Jul 19 2018 at 22:29):

here is what my local package cache looks like ( I just built US-Core locally)
Screen-Shot-2018-07-19-at-3.26.41-PM.png

Eric Haas (Jul 19 2018 at 22:30):

and here is my dependency for US Core dev: ( ignore the fact that is a csv file)

dependencyList.name,uscore
dependencyList.location,http://hl7.org/fhir/us/core
dependencyList.source,dependencies/uscore-vp
dependencyList.version,dev

Eric Haas (Jul 19 2018 at 22:32):

so in theory this should work......

Bryn Rhodes (Jul 19 2018 at 22:33):

Okay, that was it, thanks @Grahame Grieve , the version needs to be dev:

Bryn Rhodes (Jul 19 2018 at 22:33):

"dependencyList": [
{
"name": "qicore",
"location": "http://hl7.org/fhir/us/qicore",
"version": "dev"
}
],

Bryn Rhodes (Jul 22 2018 at 16:16):

So this worked to get a local build, but when I push it, the CI build fails. How can I get the dev QI-Core loaded into the package cache used by the CI build?

Grahame Grieve (Jul 22 2018 at 19:22):

hmm should automatically downgrade to current on the CI build

Grahame Grieve (Jul 22 2018 at 19:23):

does current work for you?

Bryn Rhodes (Jul 22 2018 at 20:28):

It should, but I think it can't resolve because the package-list isn't present on the canonical IG site.

Grahame Grieve (Jul 22 2018 at 20:30):

current is not resolved via package-list.

Bryn Rhodes (Jul 22 2018 at 21:05):

I tried changing to current locally but it says it can't resolve the package list. I just pushed the change to the repository to see if it behaves differently there.

Bryn Rhodes (Jul 22 2018 at 21:06):

It just errored: Publishing Content Failed: Error fetching package list for hl7.fhir.us.qicore from http://hl7.org/fhir/us/qicore/package-list.json: http://hl7.org/fhir/us/qicore/package-list.json

Bryn Rhodes (Jul 22 2018 at 21:06):

I tried changing the canonical reference to the build url, but then got a canonical mismatch.

Grahame Grieve (Jul 23 2018 at 04:18):

I'll have a look soon. I'm close to catching up on applying all the substantiative changes for R4

Grahame Grieve (Jul 23 2018 at 04:18):

at least for the foundation

Bryn Rhodes (Jul 29 2018 at 20:31):

Pinging on this, is there a workaround that I can use to get the HEDIS-IG back up?

Grahame Grieve (Jul 29 2018 at 23:45):

can I reproduce this?

Bryn Rhodes (Jul 30 2018 at 18:47):

Should be able to by just cloning the hedis-ig and running it. With the Qi-core version set to current, it tries to download the package from the canonical uri. https://github.com/cqframework/hedis-ig

Christopher Schuler (Aug 07 2018 at 16:37):

@Grahame Grieve were you able to repro this issue?

Grahame Grieve (Aug 07 2018 at 20:38):

no but it's on my list for today

Christopher Schuler (Aug 07 2018 at 21:14):

Awesome, thank you sir!

Grahame Grieve (Aug 09 2018 at 03:26):

ok this should be fixed once the next build completes

Christopher Schuler (Aug 09 2018 at 05:09):

Yessir, that did the trick. Thanks!

Last updated: Apr 12 2022 at 19:14 UTC