Hi all - is it possible that there are server errors right now with packages2.fhir.org ? I'm seeing a lot of timeout errors leading to build failures: Assign Comparison Ids (00:00.003 / 01:27.983, 1Gb) Propagating status (00:00.000 / 01:27.983, 1Gb) Generating Narratives (00:00.000 / 01:27.983, 1Gb) Validating Conformance Resources (00:00.318 / 01:28.302, 1Gb) Error fetching https://packages2.fhir.org/packages/hl7.terminology.r5 : Read timed out Error fetching https://packages2.fhir.org/packages/hl7.fhir.uv.extensions.r5 : Read timed out Failed to determine latest version of package hl7.fhir.uv.extensions.r5 from server: https://packages2.fhir.org/packages Error fetching https://packages2.fhir.org/packages/hl7.cda.us.ccda : Read timed out Error fetching https://packages2.fhir.org/packages/hl7.cda.uv.core : Read timed out Failed to determine latest version of package hl7.cda.uv.core from server: https://packages2.fhir.org/packages Failed to determine latest version of package hl7.cda.uv.core from server: https://packages.fhir.org Failed to determine latest version of package hl7.cda.uv.core from server: build.fhir.org Latest version of package hl7.cda.uv.core found locally is 2.0.1-sd - using that

hmm

no looks like it's all good to me

My commit just failed and seeing similar issues as well. When build locally, it builds successfully. Error fetching https://packages2.fhir.org/packages/hl7.fhir.us.core.3.1.1 : Not Found Error fetching https://packages.fhir.org/hl7.fhir.us.core.3.1.1 : Not Found Publishing Content Failed: Unable to resolve package id hl7.fhir.us.core.3.1.1#3.1.1 Here is the link to the log: https://build.fhir.org/ig/HL7/davinci-vbpr/branches/master/failure/build.log

@Grahame Grieve

To make this clear, the VBPR 1.1 IG itself does not have any dependency on US Core 3.1.1. The dependency IGs have reference to US Core 3.1.1. I am not able to make any updates to how the 3.1.1 package is referenced in those published IGs. How should I resolve this? My commit to CI Build fails. This wasn't an issue about 3 weeks ago.

this should be sorted now

It works now, thank you!

Hi @Grahame Grieve , I also have a possible issue on packages2.fhir.org . The package de.basisprofil.r4#1.5.x can't be found. On the server only the 1.6 packages are available: https://packages2.fhir.org/packages/de.basisprofil.r4

I see that these are published through simplifier

The simplifier API is rate limited; I expect that packages2.fhir.org will get the other versions in a few days time.

this happened because I had a server disaster and my DR plan is to install from scratch. That works really well except for simplifier - I will consider that

Ok thanks, unfortunately this breaks my CI. But I also have no cache for the packages. So also a problem on my side.

sorry to hear that.

you should take it up with simplifier. All the rate limit achieves is more hits on their server

at least from me

IHMO a rate limit is always a good idea. I'll establish a cache so that I not depend too much on the central package server.

I guess. I run with rate limits too, but they're much higher

Did something change in the fetching "algorithm". Since yesterday I get: https://build.fhir.org/ig/RIVO-Noord/zorgviewer-ig/branches/__default/failure/build.log Installing nictiz.fhir.nl.stu3.eafspraak#1.0.6 done. Installing nictiz.fhir.nl.stu3.zib2017#2.0.x to the package cache Fetching: Publishing Content Failed: Invalid criteria: null.x: (Expected numeric identifier at position 0) (00:10.538 / 00:29.949, 256Mb) No problems before yesterday with same version of the IG publisher, same version of the dependencies.

yes some problems on the package server

how do I reproduce?

Rebuild the zorgviewer-ig. Or do you need something else?

what's the github repo?

https://github.com/RIVO-Noord/zorgviewer-ig

I don't know why it worked in the past, but the simplifier package has a wildcard dependency and these aren't supported - yet

I will be able to address this in 10 days time - disappearing off into the bush

it's not a simple fix, it's building out new infrastructure. So I might not be able to address it

Is this different than the situation that arose last september ?

I don't know - records have been scrubbed since then

I just don't understand. The CI-build keeps failing, but my local build just works fine. What am I missing here?

I don't know why your local build works. what you're doing is not supported

When I run this locally the IG Publisher installs a specific version 2.0.6 and when I run the same on in the CI build it wants a version 2.0.x.

The strange thing is that up to januari 14th (v2.0.29) it worked fine. After that it failed.

I checked the GH action build log and found that starting 15-jan (still v2.0.29) it failed. So it looks to be something in the package repo.

i revise my opinion. It should work, and looks like it does on ci-build

Yesterday I removed the dependency with the package that had the "2.0.x" dependency. So that now works. You mean that I can reintroduce the dependency and it should work now?

well, try again, and I'll have a look if it doesn't

I created a branch with the issue in it and the CI build failed :-(. https://build.fhir.org/ig/RIVO-Noord/zorgviewer-ig/branches/eafspraak-2.0.x/failure/build.log