FHIR Chat · Debugging IG generation · shorthand

Stream: shorthand

Topic: Debugging IG generation

Nick Goupinets (Mar 17 2021 at 19:58):

It's my day 3 with FSH/IG wizardry, so any help is greatly appreciated. I am trying to build a basic profile to include extension containing address validation results to the Address. The intent is to have a at most one validation results extension on Organization for now:

Profile: MyOrganization
Parent: Organization
Id: My-organization
Title: "Organization"
Description: "A profile on the Organization resource for My Organization."

• address.extension contains MyValidatedAddressExtension named MyValidatedAddressExtension 0..1

Extension: MyValidatedAddressExtension
Title: "My Validated Address"
Description: "Address that's been validated by an external service."

• value[x] only code

• valueCode from MyAddressValidationResultsValueS
  ValueSet: MyAddressValidationResultsValueSet
  Title: "My Address Validation Value Set"
  Description: "My Address Validation Value Set"

• include codes from system ExternalAddressValidationResultsCodeSystem

CodeSystem: ExternalAddressValidationResultsCodeSystem
Title: "External Address Validation Results Code System"
Description: "Code System for External Address Validation Results"

• ^url = "https://www.external.org/AddressValidation"
• #valid "Valid" "Valid Address as validated by an external service"
• #invalid "Invalid" "Invalid Address as validated by an external service"
• #not-validated "Not-Validated" "Unable to validate address by an external service"

This mostly works except when I am building IG, qa.html contains this error:

StructureDefinition/ValidatedAddressExtension: StructureDefinition Process Info Validate resource against profile http://hl7.org/fhir/StructureDefinition/StructureDefinition
StructureDefinition/ValidatedAddressExtension: StructureDefinition.snapshot.element[3].fixed.ofType(uri) error The element Extension.url has a fixed of type uri, which is not in the list of allowed types ([http://hl7.org/fhirpath/System.String])

Is it a showstopper? What am I doing wrong?

Chris Moesel (Mar 17 2021 at 20:16):

This is a known bug recently introduced in the IG Publisher. They're working on fixing it. It's discussed here and here.

Chris Moesel (Mar 17 2021 at 20:19):

BTW -- welcome to the FSH community! We're glad you're here. Here's a pro-tip: you can share short(ish) FSH snippets via FSH Online. For example, here is a link to the code you posted above: https://fshschool.org/FSHOnline/#/share/3tAocLJ

Nick Goupinets (Mar 17 2021 at 21:34):

Thank you Chris! With so much support, I am here to stay :)

Chris Moesel (Mar 17 2021 at 21:40):

Oh sorry. Forgot to tell you. Only the first two are free -- and it looks like you already used yours. The next one is $59.95 (or you can buy a 2-pack for $99.95). ;-)

Chris Moesel (Mar 17 2021 at 23:09):

That was a joke, by the way. Always glad to help!

Jean Duteau (Mar 17 2021 at 23:10):

Chris Moesel said:

That was a joke, by the way. Always glad to help!

He says it's a joke, but you won't be laughing when the bill shows up at your office! I'm okay with paying for support, but I thought the $25k bill was a bit excessive!

Lloyd McKenzie (Mar 18 2021 at 01:45):

He has a special price just for you Jean...

David Pyke (Mar 18 2021 at 11:54):

Hey! I'm paying $139.95 a month for my support with a maximum of one issue per month! How come he gets a deal?!?

David Pyke (Mar 18 2021 at 11:54):

Chris needs to post his rates. None of this discriminating against Canadians!

Simone Heckmann (Mar 18 2021 at 11:56):

29,99€ for shipping chat messages to Germany!? ARE YOU KIDDING ME????

John Moehrke (Mar 18 2021 at 12:12):

don't foget about surge pricing

Chris Moesel (Mar 18 2021 at 12:53):

@David Pyke -- the prices reflect how difficult you are to deal with. Each person has their own rate. So if your rate seems high, well...

David Hay (Mar 21 2021 at 21:45):

I'm almost scared to ask what my rate is...

Chris Moesel (Mar 22 2021 at 12:48):

@David Hay -- We give you a discount since you promote FSH on your blog and in your tooling.

Nick Goupinets (Mar 31 2021 at 20:59):

Lol, this is funny. To be honest, FSH is such a fantastic tool, any it would be easy to justify any reasonable support costs :)

Jean Duteau (Mar 31 2021 at 21:00):

shh @Nick Goupinets don't give them ideas!

Janaka Peiris (Apr 20 2021 at 06:06):

My IG generation is stuck from here (after line "Sushi: info Converted 28 FHIR StructureDefinitions"). Had errors in the profile, which has been corrected, but this seems something not related to that:
image.png

I notice Node.js component using 500+MB since running IG tool (see image)
image.png

temp/qa folder too is not updated, so this means it has not come upto this stage.

Is there a way to see a debug output ?

Chris Moesel (Apr 20 2021 at 12:26):

That looks like either you have a lot of CodeSystem/ValueSet/Instances (since it does those next after StructureDefinitions) or SUSHI is trying to load some large sub-folder in the project. Does it work OK outside of the IG Pubisher (if you run sushi directly)? Outside of the publisher, you can turn on SUSHI debug output via the -d flag -- but, honestly, we don't provide many additional debug statements.

I have also seen cases where the IG Publisher does not handle long log statements from SUSHI well and it stops printing them to the console -- so it appears it is stuck even though it isn't. Have you tried just waiting a while to see if it eventually picks up again?

Christian Nau (Apr 20 2021 at 12:32):

IG generation takes some time for me as well (~15min) and it looks like it is stuck during this progress. Unless you haven't tried this I would suggest that you "just wait" for a good amount of time (as @Chris Moesel also said)

Janaka Peiris (Apr 20 2021 at 12:42):

This IG generates fine with a minimal setup. Also, I have kept it for longer periods (> 30 mins). So I'll try reducing the no of StuctureDefinitions and other sub-items as much as possible, thanks for the tip of running just Sushi, as its colored output helps save me a lot of time. So I will figure out to fix the errors first.

Janaka Peiris (Apr 23 2021 at 06:57):

I have sushi giving me no errors, also included dependencies in sushi-config.yaml:

dependencies:
  hl7.fhir.no.basis:
    uri: https://simplifier.net/packages/hl7.fhir.no.basis/2.0.11
    version: 2.0.11

But getting this error, any idea why ?

Publishing Content Failed: Error generating snapshot for HnDomainVitalSignsObservationBloodpressure(HnDomainVitalSignsObservationBloodpressure): Cannot find or generate snapshot for base definition (http://hl7.no/fhir/StructureDefinition/no-domain-vitalsignsobservation-bloodpressure from http://dips.no/StructureDefinition/HnDomainVitalSignsObservationBloodpressure) (00:26.0176)

image.png

Patrick Werner (Apr 23 2021 at 09:19):

The reason is, that Simplifier doesn't include snapshots in their FHIR packages.

Patrick Werner (Apr 23 2021 at 09:20):

workaround is to download the package directly from Simplifier, you can then choose download with snapshots, and then replace the version in your local fhir package cache with the snapshotted one.

Patrick Werner (Apr 23 2021 at 09:20):

I hope Simplifier will address this issue soon.

Janaka Peiris (Apr 23 2021 at 12:02):

@Patrick Werner tried your solution by manually replacing the local package cache, but it doesn't seem to pick that up. I tried specifying the dependencies as below, still no luck. Since the URI is needed, won't it always fetch from there ?

dependencies:
  hl7.fhir.no.basis: 2.0.11

Janaka Peiris (Apr 23 2021 at 12:07):

Also, there are many dependencies to this package ( hl7.fhir.no.basis ), so do we need those added under YAML file dependencies as well? I don't see much documentation around this, all say just add the URI.
image.png

Patrick Werner (Apr 23 2021 at 12:34):

yes transitive dependencies (if they are coming from simplifier) are still another problem. You have to manually d/l each one of these and add them to your cache

Patrick Werner (Apr 23 2021 at 12:35):

This is the thread discussing this issue: https://chat.fhir.org/#narrow/stream/215610-shorthand/topic/Dependencies

Janaka Peiris (Apr 23 2021 at 12:52):

ok, thanks will continue my question there, as the topic of this post is different

Chris Moesel (Apr 23 2021 at 12:53):

Usually the issue w/ Simplifier not publishing snapshots causes problems with SUSHI. In this case, however, @Janaka Peiris reports that SUSHI does fine and it is actually causing an issue in the IG Publisher. So does the IG Publisher also not handle the Simplifier packages well, @Patrick Werner?

Janaka Peiris (Apr 23 2021 at 12:58):

As suggested by @Patrick Werner I was able to get SUSHI working. Downloaded profiles into C:\Users\<user>\.fhir\packages\hl7.fhir.no.basis#dev with snapshot and SUSHI was ok("Sushi: info Loaded package hl7.fhir.no.basis#dev"):

dependencies:
  hl7.fhir.no.basis:
    uri: https://simplifier.net/packages/hl7.fhir.no.basis/2.0.11
    version: dev

Yet the same error comes with IG Publisher.

Janaka Peiris (Apr 27 2021 at 07:20):

@Chris Moesel @Patrick Werner Do you know how I can get IG Publisher (publisher.jar) to use the same approach as in Sushi, and get it to refer updated packages from local cache ?

Oliver Egger (Apr 27 2021 at 07:55):

the IG Publisher can also use dev dependencies, provide the package name and the version 'dev'. maybe you need to remove the uri?

Janaka Peiris (Apr 27 2021 at 09:09):

URL in dependencies is needed for Sushi to validate, otherwise it stops with error:

Failed to add hl7.fhir.no.basis:dev to ImplementationGuide instance because SUSHI could not find the IG URL in the dependency IG. To specify the IG URL in your sushi-config.yaml, use the dependency details format:

So this is the error IG Publisher still gives:

Cannot find or generate snapshot for base definition

Chris Moesel (Apr 27 2021 at 12:57):

The error reported by SUSHI is that it cannot determine the canonical URL to the IG from the package. This is required because ImplementationGuide.dependsOn.uri is 1..1 -- so we need to have it when we generate the ImplementationGuide. Usually we search the package for an instance of ImplementationGuide w/ the specified package ID and then extract the URL from that. But many (most?) Simplifier packages don't have an ImplementationGuide at all, so there is nothing to extract it from. Which is why we ask the user to provide it in the sushi-config.yaml in those cases.

This, however, is a separate issue from the IG Publisher error Cannot find or generate snapshot for base definition. If I am to take that one at face value, it sounds like it can't find a snapshot in a base definition (presumably the base for one of your profiles). I actually don't fully understand the issue, however, because I thought that the IG Publisher generated snapshots when they weren't there (unlike SUSHI, which does not have that capability). So... I am already a little confused by that. When SUSHI can't find a snapshot in a dependency, the solution is to download a version of the package w/ snapshots in it and manually copy that into your local FHIR cache (which I described here, and I think you're already aware of). Are you saying that when you do that, the IG Publisher still doesn't seem to recognize the snapshots in your package?

Grahame Grieve (Apr 27 2021 at 19:58):

usually it means that snapshot generation failed for that base, and there should be an error in the output

Janaka Peiris (Apr 29 2021 at 07:26):

@Chris Moesel Yes, I've already copied the package with snapshot and was able to get SUSHI to validate without errors. So it's the IG Publisher I have this error now. After your explanation, I checked the input/ImplementationGuide resource json file and noticed that doesnt have dependsOn property, and may be this is why IG Publisher is unable to proceed. So I tried adding it as follows:

  "dependsOn":[
    {
      "uri": "https://simplifier.net/packages",
      "packageId" : "hl7.fhir.no.basis",
      "version": "2.0.11"
    }
  ],

Now the error has changed to:

Load Package hl7.fhir.pubpack#0.0.7
Load Package hl7.fhir.xver-extensions#0.0.5
Load Package hl7.terminology.r4#2.1.0
Dependency 'hl7.fhir.no.basis' has no id, so can't be referred to in markdown in the IG (00:25.0066)
Publishing Content Failed: no core dependency or FHIR Version found in the Package definition (00:25.0077)

I see that it tries to load hl7.fhir.no.basis, so it must be fetching it from the url. Then I checked the packages.json, and found 2 mandatory properties are missing (fhirVersions and author). Tried manually updating the values in my local cache, still it doesn't seem to pick that up.

So Is there a way I can get the local copy (with snapshot) to be referred by IG Publisher, as we did in Sushi with version: dev ? (already tried as "version": "dev" but IG Pub gives the same error)

Janaka Peiris (Apr 29 2021 at 09:35):

I've tested with newer versions of package hl7.fhir.no.basis and that 2.0.16-beta seems to have corrected those errors. Now checking next error with those...

Janaka Peiris (May 04 2021 at 16:56):

I had to go through source code of IG Publisher from Publisher.java to figure out this error:

Load Package hl7.terminology.r4#2.1.0
Publishing Content Failed: JsonNull                                              (00:23.0388)
                                                                                 (00:23.0390)
Use -? to get command line help                                                  (00:23.0392)
                                                                                 (00:23.0398)
Stack Dump (for debugging):                                                      (00:23.0401)
java.lang.UnsupportedOperationException: JsonNull
        at com.google.gson.JsonElement.getAsString(JsonElement.java:192)
        at org.hl7.fhir.utilities.npm.NpmPackage.getWebLocation(NpmPackage.java:818)
        at org.hl7.fhir.igtools.publisher.Publisher.loadIg(Publisher.java:2789)
        at org.hl7.fhir.igtools.publisher.Publisher.initializeFromIg(Publisher.java:1909)
        at org.hl7.fhir.igtools.publisher.Publisher.initialize(Publisher.java:1461)
        at org.hl7.fhir.igtools.publisher.Publisher.execute(Publisher.java:729)
        at org.hl7.fhir.igtools.publisher.Publisher.main(Publisher.java:8429)

@Chris Moesel This error was due to the "url" property of fhir package, which was null. Its great if it can be given an error message instead of an exception. Since I had my local cache with "fhir package with snapshot" downloaded as a dev version, I manually edited the packages.json and included 'url' with same value from simplifier package repo. Then it solved above issue, but I have to continue finding an answer for the next error.

Janaka Peiris (May 04 2021 at 17:11):

https://confluence.hl7.org/display/FHIR/NPM+Package+Specification: says url of packages.json is optional, so then IG Publisher should handle that error, isnt it ?

Package Manifest Properties

url - optional - where the human readable representation (e.g. IG) that represents this version of this package is published on the web (if there is such a thing)

Janaka Peiris (May 04 2021 at 17:41):

@Espen Stranger Seland , @Thomas Tveit Rosenlund Do you know of an Implementation Guide created using the fhir package hl7.fhir.no.basis ver 2.0.16-beta (or any other version) ? I'm following the FHIR Shorthand path as per https://fshschool.org/docs/sushi/project/.

Either my files need a lot of changes, or I'm not sure if I'm missing something here, as anyone who had tried this approach should have faced the above issues using the IG Publisher. On the other hand, there are so many IGs created and published using IG Publisher tool (I assume). Let me know if you know of any such Norwegian IGs so I can refer. Thanks

Thomas Tveit Rosenlund (May 04 2021 at 18:10):

@Janaka Peiris Sorry about this, I did not realize that IG generation using SUSHI and IG publisher was such a pain with the no-basis packages. As you noted the 2.0.16-beta version did fix some issues reported by the java-validation tool, and I am glad to see that this actually did help somewhat.

Our current production pipeline involves Forge and SIMPLIFIER as tools for publishing. But if there are problems using the SIMPLIFIER packages for IG generation using the java tooling and SUSHI this is actually a big deal for us. I have been interested in looking into IG generation using standard tooling for some time now, but other pressing issues have gotten the best of me so far unfortunately. Anyways, please let us know if there are any other bugfixes we could provide to the packages/source-code of no-basis to make the SUSHI/IG-publisher pipeline work as intended.

I don't know of any projects in Norway using the IG-publisher pipeline currently, as we invested in the SIMPLIFIER tooling early on and most major projects are using that pipeline for FHIR documentation.

Chris Moesel (May 04 2021 at 19:26):

Thanks for all of the information, @Janaka Peiris. I'm not sure if I fully followed everything, but it seems like you have figured some things out.

If there is SUSHI output (generated in the fsh-generated folder) that needs to be changed, please let me know and I can see if we can fix it in SUSHI. For issues w/ the IG Publisher, however, it's probably best to reach out to Grahame, as I (and the FSH/SUSHI) team do not work on the IG Publisher.

Janaka Peiris (May 05 2021 at 04:25):

Thanks @Thomas Tveit Rosenlund and @Chris Moesel , I will post updates as I figure out solutions, as that would help anyone generating IGs using these Norwegian national base packages.

Janaka Peiris (May 05 2021 at 04:31):

@Grahame Grieve I think this might need a fix in IG Publisher, as it should not end up with an error for an optional property in packages.json isn't it ? If this should be reported, I'll add details.

Grahame Grieve (May 05 2021 at 04:35):

I'm not sure why the url is present and null?

Janaka Peiris (May 05 2021 at 05:02):

Yes, so I tried removing the url property, then IG Publisher didn't complain. The error was when it tries to get a string out of a "defined" property, which is null.

@Thomas Tveit Rosenlund as @Grahame Grieve mentions, maybe we should check the rest of the properties with null and remove those to avoid any issues:

packages.json from https://simplifier.net/packages/hl7.fhir.no.basis/2.0.16-beta:

{
  "name": "hl7.fhir.no.basis",
  "version": "2.0.16-beta",
  "description": "Norwegian core profiles for R4\r\nversion 2.0.16-beta",
  "author": "thomiz",
  "fhirVersions": [
    "4.0.1"
  ],
  "dependencies": {
    "hl7.fhir.core": "4.0.1",
    "hl7.fhir.r4.core": "4.0.1"
  },
  "devDependencies": null,
  "keywords": null,
  "license": null,
  "homepage": null,
  "directories": null,
  "title": null,
  "fhir-version-list": null,
  "maintainers": null,
  "canonical": null,
  "url": null,
  "jurisdiction": null
}

Grahame Grieve (May 05 2021 at 05:22):

it's certainly not something I expected, that you'd have null there, instead of no property, and because of the way gson (google json library) works, they'll all produce NPEs. Or some of them anyway. the urlproperty won't after the next release

Thomas Tveit Rosenlund (May 05 2021 at 10:26):

@Janaka Peiris You could try using my updated packages.json https://simplifier.net/HL7Norwayno-basis/package.json/~overview

Is should be available as part of the package download starting from the next package version we publish.

Janaka Peiris (May 07 2021 at 09:09):

@Thomas Tveit Rosenlund let me know once this new package is updated in Simplifier. Though the modified FHIR package in local cache is picked up correctly by SUSHI (ver: dev), it seems the IG Publisher is still referring other (ver: 2.0.16-beta). So when 2 packages are being referred, there could be issues. I have put this on hold as going through code to investigate is taking more time to resolve.

Ward Weistra (May 12 2021 at 11:52):

@Thomas Tveit Rosenlund Thoughts on how those null values came there originally?

Ward Weistra (May 12 2021 at 12:17):

@Thomas Tveit Rosenlund I learned I can answer my own question, our package library may have introduced them previously. We also already published a fix, which will remove the null values from package.json on any newly created package version.

Ward Weistra (May 12 2021 at 12:19):

@Grahame Grieve You might still want to put error handling in place for ignoring any package manifest parameters that have a null value? (If only because we can't remove this from package manifests from already published packages)

Thomas Tveit Rosenlund (May 12 2021 at 12:47):

@Ward Weistra Correct, SIMPLIFIER put them in there. I could fix this myself by editing the package.json file. Nice to hear you have fixed this!

Ward Weistra (May 12 2021 at 13:49):

@Thomas Tveit Rosenlund Thanks for confirming. Sorry for the trouble!

Grahame Grieve (May 13 2021 at 00:14):

I added it for this one. I'll review the others at some stage

Janaka Peiris (May 31 2021 at 09:31):

@Thomas Tveit Rosenlund is there a plan to upload a new package, latest I still see is still hl7.fhir.no.basis 2.0.16-beta at https://simplifier.net/HL7Norwayno-basis/~packages

Thomas Tveit Rosenlund (May 31 2021 at 09:51):

Janaka Peiris said:

Thomas Tveit Rosenlund is there a plan to upload a new package, latest I still see is still hl7.fhir.no.basis 2.0.16-beta at https://simplifier.net/HL7Norwayno-basis/~packages

Yes, but it will be an excact copy of the beta. Have not found any other bugs in the beta version (except the packaging definition that is fixed now).

Janaka Peiris (Jun 02 2021 at 04:54):

@Grahame Grieve I'm trying to debug the following error (), so I was checking the Git repo at:
https://github.com/HL7/fhir-ig-publisher/blob/master/org.hl7.fhir.publisher.core/src/main/java/org/hl7/fhir/igtools/publisher/Publisher.java

java.lang.Exception: Error generating snapshot for HnDomainVitalSignsObservationBloodpressure(HnDomainVitalSignsObservationBloodpressure): Cannot find or generate snapshot for base definition (http://hl7.no/fhir/StructureDefinition/no-domain-vitalsignsobservation-bloodpressure from http://dips.no/StructureDefinition/HnDomainVitalSignsObservationBloodpressure)
        at org.hl7.fhir.igtools.publisher.Publisher.generateSnapshots(Publisher.java:4522)

Q:
1) I see org.hl7.fhir.r5.model.* are used from master branch, is there a different branch that uses R4 models ?

2) I tried downloading the project and just building it using "mvn install -e", then I get this error. Is there anything i'm missing ?

image.png

Grahame Grieve (Jun 02 2021 at 05:08):

@Mark Iantorno will let you know when the IG publisher compiles again

Grahame Grieve (Jun 02 2021 at 05:08):

the IG publisher is all R5 internally

Jose Costa Teixeira (Jun 02 2021 at 13:34):

Chris Moesel said:

When SUSHI can't find a snapshot in a dependency, the solution is to download a version of the package w/ snapshots in it and manually copy that into your local FHIR cache (which I described here, and I think you're already aware of). Are you saying that when you do that, the IG Publisher still doesn't seem to recognize the snapshots in your package?

Is there a more humane way of doing this already?

Jose Costa Teixeira (Jun 02 2021 at 13:35):

Is there a way for sushi to say "no wait, if the package is from simplifier, I'm going to make sure I download the snapshot-enabled package"
?

Janaka Peiris (Jun 02 2021 at 13:43):

@Jose Costa Teixeira
For Sushi, this is possible by setting the version to "dev" . I've done this already and Sushi detects local package cache correctly. But what I dont know is if the IG Publisher tool does the same (take local cache without reaching the URL).
eg:

dependencies:
  hl7.fhir.no.basis:
    uri: https://simplifier.net/packages/hl7.fhir.no.basis/
    version: dev

Jose Costa Teixeira (Jun 02 2021 at 13:58):

that just tells me that the package should be installed locally before (manually, which is what I want to avoid)

Jose Costa Teixeira (Jun 02 2021 at 13:58):

Falling back to ehealthplatform.be.r4.federalprofiles#current since ehealthplatform.be.r4.federalprofiles#dev is not locally cached. To avoid this, add ehealthplatform.be.r4.federalprofiles#dev to your local FHIR cache by building it locally with
the (00:06.0432)

Chris Moesel (Jun 02 2021 at 14:06):

@Jose Costa Teixeira, there is not yet a "more humane" way of handling Simplifier packages that don't have snapshots. Unfortunately, Simplifier does not provide an API for downloading the package with snapshots (otherwise we would use it!). Only authenticated users can download the snapshot-enabled packages (through a browser) -- which is why updating the FHIR cache is still a manual process.

Jose Costa Teixeira (Jun 02 2021 at 14:09):

ah ok that is what I was missing

Jose Costa Teixeira (Jun 02 2021 at 14:10):

there is a GET request for getting the package with snapshots, but it requires authentication indeed...

Jose Costa Teixeira (Jun 02 2021 at 14:11):

is there any expectation that in the future this would be handled? I guess the change would need to be on simplifier @Ward Weistra ?

Chris Moesel (Jun 02 2021 at 14:11):

I'd still like to see if there are things we can do to make it a little easier (if nothing else, providing polished documentation on how to do it) -- but right now releasing SUSHI 2.0 w/ logical models, custom resources, indent contexts, and enhanced CodeSystem syntax is top priority!

Chris Moesel (Jun 02 2021 at 14:14):

For reference, here is a conversation from March/April covering some of these topics w/ feedback from Ward as well: https://chat.fhir.org/#narrow/stream/215610-shorthand/topic/Dependencies

Jose Costa Teixeira (Jun 02 2021 at 14:40):

Right, I did not find that threadt, thanks.

Jose Costa Teixeira (Jun 02 2021 at 14:41):

I'll continue the discussion over there

Julian Sass (Jun 03 2021 at 14:43):

Patrick Werner said:

workaround is to download the package directly from Simplifier, you can then choose download with snapshots, and then replace the version in your local fhir package cache with the snapshotted one.

Can anybody point me in the direction where the package cache is on mac? I checked /Library/Caches and /Users/{user}/Library/Caches but can't find it. I have the .fhir folder on my windows machine, but no such thing on my mac.

Oliver Egger (Jun 03 2021 at 14:48):

cd ~
ls .fhir

Oliver Egger (Jun 03 2021 at 14:48):

in your home directory /Users/{user}

Julian Sass (Jun 03 2021 at 14:50):

Thanks @Oliver Egger :smile:

Janaka Peiris (Jun 08 2021 at 06:12):

Grahame Grieve said:

Mark Iantorno will let you know when the IG publisher compiles again

I was able to load project using Eclipse IDE and Debug. Issues I faced were:
1) I had taken a copy of the code using a ZIP file than cloning the GIT repo. So my local folder did not have branch information. There was an error mentioned while running Maven compile. Cloning is needed.
2) Still there were few errors in org.hl7.fhir.igtools.publisher.Publisher.java. But all those could be corrected just by following suggestions (I guess those arent critical).

Just shared this, for anyone wanting to debug the IG errors and find reasons.

Janaka Peiris (Jun 14 2021 at 16:36):

Pls download the latest IG Generator tool, as there are some fixes. I've had many issues trying to debug using Eclipse and manually running Jekyll to get this generated.

Thanks a lot @Mark Iantorno for the updates !

Peter Robinson (Jun 14 2021 at 19:02):

Thanks, @Janaka Peiris -- to be specific, I am able to generate the IG without problems locally, it is just not getting hooked up to github IO.

Last updated: Apr 12 2022 at 19:14 UTC