Stream: tooling
Topic: Package importer
Ward Weistra (Jan 11 2022 at 15:54):
@Grahame Grieve Here's the relevant errors from the most recent run of the package importer, getting the data from the feeds in https://github.com/FHIR/ig-registry/blob/master/package-feeds.json:
Skipping hl7.fhir.us.phcp-0.1.0. The Fhir version was not recognized: 3.1.0.
Skipping hl7.fhir.us.phcp-0.2.0. The Fhir version was not recognized: 3.1.0.
Processing: FHIR Foundation Guides: http://fhir.org/guides/package-feed.xml
Skipping fhir.argonaut.pd-0.1.0. The Fhir version was not recognized: 1.9.0.
Skipping fhir.hspc.core-0.1.0. The Fhir version was not recognized: 1.9.0.
Processing: FHIR Foundation Support Packages: http://fhir.org/packages/package-feed.xml
Skipping fhir.dicom-2021.4.20210910. The Fhir version was not recognized: current.
Skipping fhir.dicom-2021.5.20211122. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r3-0.10.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r3-0.11.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r3-0.12.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r3-0.13.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r3-0.14.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r3-0.15.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r3-0.16.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r3-0.17.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r4-0.10.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r4-0.11.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r4-0.12.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r4-0.13.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r4-0.14.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r4-0.15.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r4-0.16.0. The Fhir version was not recognized: current.
Skipping fhir.tx.support.r4-0.18.0. The Fhir version was not recognized: current.
There's also a bunch of packages being skipped because of:
- R4B, R5 -> We're expecting to support these versions in Simplifier and the package importer in the coming weeks
- Missing FHIR version -> We're building support for importing these, which we also hope to release coming weeks
Ward Weistra (Jan 12 2022 at 17:03):
Ah, a few more that were relevant, inconsistencies between the listing in the feed and in the actual package.json in the package:
Downloading package: hl7.fhir.us.immds version: 0.1.0
Publishing to: https://packages.simplifier.net
400 BadRequest -- Package version '0.1.0' already exists for package 'hl7.fhir.uv.immds'
Downloading package: hl7.fhir.us.immds version: 0.2.0
Publishing to: https://packages.simplifier.net
400 BadRequest -- Package version '0.2.0' already exists for package 'hl7.fhir.uv.immds'
Downloading package: hl7.fhir.us.vrdr version: 1.1.0
Publishing to: https://packages.simplifier.net
400 BadRequest -- Package version '1.2.0' already exists for package 'hl7.fhir.us.vrdr'
And for @John Moehrke (or secretary@ihe.net):
Downloading package: ihe.mhd.fhir version: 4.0.0
Publishing to: https://packages.simplifier.net
400 BadRequest -- Package version '4.0.0-comment' already exists for package 'ihe.mhd.fhir'
Downloading package: ihe.pdqm.fhir version: 2.2.1
Publishing to: https://packages.simplifier.net
400 BadRequest -- Package version '2.2.1' already exists for package 'IHE.ITI.PDQm'
John Moehrke (Jan 12 2022 at 17:06):
I think the pdqm thing is because I have moved the ci-build to lowercase. right? thus you got one ci-build when it was uppercase and now the ci-build is lowercase... formal release is still uppercase. ---- I don't know if this is proper, no one helped me.
John Moehrke (Jan 12 2022 at 17:07):
the mhd... I think that 4.0.0-comment was last year. MHD is now released at 4.0.2
John Moehrke (Jan 12 2022 at 17:08):
let me understand what I can do to help. I am not sure I understand the issue or how to help
Ward Weistra (Jan 12 2022 at 17:16):
@John Moehrke It's not just a capitalization issue. The details in your feed for the respective packages are not in line with what really is in the package manifest file that is referred to. For example:
<item>
<title>ihe.mhd.fhir#4.0.0</title>
[...]
<link>https://profiles.ihe.net/ITI/MHD/4.0.0/package.tgz</link>
<guid isPermaLink="true">https://profiles.ihe.net/ITI/MHD/4.0.0/package.tgz</guid>
[...]
</item>
But the package.json for that file reads:
{
"name": "ihe.mhd.fhir",
"version": "4.0.0-comment",
[...]
}
Since they are inconsistent the importer doesn't know what the version needs to be, hence the importing is skipped.
Ward Weistra (Jan 12 2022 at 17:19):
Same for:
<item>
<title>ihe.pdqm.fhir#2.2.1</title>
[...]
</item>
vs
{
"name": "IHE.ITI.PDQm",
[...]
}
Grahame Grieve (Jan 14 2022 at 01:03):
@Ward Weistra I agree that hl7.fhir.us.phcp-0.1.0 is not processible - it was based on a transient publication which was actually 3.1.0. So fine to ignore that one
Grahame Grieve (Jan 14 2022 at 01:03):
but that's not true about hl7.fhir.us.phcp-0.2.0 - looks like a processing error on your side. it's based on 4.0.1
Grahame Grieve (Jan 14 2022 at 01:05):
Also fine to ignore fhir.argonaut.pd-0.1.0 and fhir.argonaut.pd-0.1.0 - they also were really based on fhir 1.9.0
Grahame Grieve (Jan 14 2022 at 01:14):
in fact, no, I found and fixed the issue with phcp, which was the same with most of the other packages. Most should be OK now.
Grahame Grieve (Jan 14 2022 at 01:22):
@Ward Weistra it would be super useful if that information you posted above was published somewhere
Ward Weistra (Jan 14 2022 at 11:47):
Thanks @Grahame Grieve. And agreed, that's on the to do-list. Until then I'll send you (and others) one of these now and then.
Ward Weistra (Feb 02 2022 at 09:27):
@Grahame Grieve The hl7.fhir.r5.core from the package feed is a whopping 22Mb compressed. The one to download from build.fhir.org however is around 14Mb.
- Are there ways we can get that size down?
- Is there an explanation for the size difference? (Hoping it is a sign the next version will be smaller :fingers_crossed:)
Grahame Grieve (Feb 02 2022 at 09:27):
I
Grahame Grieve (Feb 02 2022 at 09:28):
I'm not sure why they're different, but does it really matter?
Ward Weistra (Feb 02 2022 at 09:29):
Everyone must download it all the time everywhere to do anything with the FHIR spec. And a halving of the size seems quite substantial.
Last updated: Apr 12 2022 at 19:14 UTC
