Stream: committers/notification
Topic: Builds failing on pubpack
Keith Boone (Apr 27 2020 at 10:19):
Since at least 5:22 builds are failing due to
org.hl7.fhir.exceptions.FHIRException: Unable to resolve package id hl7.fhir.pubpack#0.0.4
Grahame Grieve (Apr 27 2020 at 11:37):
hmm. I can't even get to that point
Patrick Werner (Apr 27 2020 at 11:50):
:+1: org.hl7.fhir.exceptions.FHIRException: Unable to resolve package id hl7.fhir.pubpack#0.0.4
Grahame Grieve (Apr 27 2020 at 12:35):
I can't get to that... still looking into it
Patrick Werner (Apr 27 2020 at 12:36):
i downloaede it manually to fix the issue
Grahame Grieve (Apr 27 2020 at 12:36):
where did you download it from?
Patrick Werner (Apr 27 2020 at 12:56):
http://fhir.org/packages/hl7.fhir.pubpack/0.0.4/
Grahame Grieve (Apr 27 2020 at 12:59):
oh - I've figured it out. It'll right in about 5 minutes
Patrick Werner (Apr 28 2020 at 07:43):
@Grahame Grieve
Now getting the error in the online IG build:
http://build.fhir.org/ig/HL7/genomics-reporting/branches/kpower_SomaticImplication/failure/build.log
Grahame Grieve (Apr 28 2020 at 07:46):
someone has found a way to pull my server over...
Jose Costa Teixeira (May 05 2020 at 10:38):
I started having this same issue now.
Jose Costa Teixeira (May 05 2020 at 10:38):
any idea how to fix?
Jose Costa Teixeira (May 05 2020 at 10:39):
local builds run fine
Grahame Grieve (May 05 2020 at 10:41):
back up package server is down.
Grahame Grieve (May 05 2020 at 10:41):
coming back now
Jose Costa Teixeira (May 05 2020 at 10:56):
thanks
Keith Boone (May 05 2020 at 12:55):
Is there something a competent person can smack (other than @Grahame Grieve ) in order to fix this when it happens? Or some other way to make sure it stops occuring?
Grahame Grieve (May 05 2020 at 13:01):
no. only me, at the moment. Coming up with a better solution is on my todo lsit
Keith Boone (May 05 2020 at 17:15):
Can you point us to where we can learn more about the current solution?
Grahame Grieve (May 06 2020 at 12:05):
well... I don't know. The packages are published via RSS feeds that are listed in https://github.com/FHIR/ig-registry/blob/master/fhir-ig-list.json. Then the package reads the RSS feeds, and indexes and stores the packages. Then the IG publisher etc use the package server to get all the packages
that all works well, except for a few packages that I use to distribute resources that are useful to the eco-system, but are not IG packages. hl7.fhir.pubpack is one - it contains all the miscellaineous files to support the web publishing. It's a valid package so far as I can tell, but packages.fhir.org has so far refused to process it.
As a result, I am still using the backup package server instead of packages.fhir.org for those packages. The backup package server runs on test.fhir.org, and someone is doing something to that serer that brings it down. I figured out what that is yet, and I don't have time right now. So when that happens, the ci-build fails.
Grahame Grieve (May 06 2020 at 12:07):
I did not expect to be using the backup package server, so didn't invest in stability for it. Perhaps I need to do that, but rihgt now, I'm just keeping ahead on a day to day basis
Last updated: Apr 12 2022 at 19:14 UTC