FHIR Chat · Weird Auto-Build Errors · IG creation

Stream: IG creation

Topic: Weird Auto-Build Errors


view this post on Zulip Chris Moesel (Jan 30 2020 at 02:44):

Autobuild is failing on the prerelease2 branch of fhir-mCODE-ig. The basic error is:

java.lang.Exception: Error Reading JSON Config file at /scratch/ig-build-temp-1MLAZ8/repo: /scratch/ig-build-temp-1MLAZ8/repo (Is a directory)
    at org.hl7.fhir.igtools.publisher.Publisher.initializeFromJson(Publisher.java:1599)
    at org.hl7.fhir.igtools.publisher.Publisher.initialize(Publisher.java:1178)
    at org.hl7.fhir.igtools.publisher.Publisher.execute(Publisher.java:657)
    at org.hl7.fhir.igtools.publisher.Publisher.main(Publisher.java:6893)
Caused by: java.io.FileNotFoundException: /scratch/ig-build-temp-1MLAZ8/repo (Is a directory)
    at java.base/java.io.FileInputStream.open0(Native Method)
    at java.base/java.io.FileInputStream.open(FileInputStream.java:213)
    at java.base/java.io.FileInputStream.<init>(FileInputStream.java:155)
    at org.hl7.fhir.utilities.TextFile.fileToString(TextFile.java:166)
    at org.hl7.fhir.utilities.json.JsonTrackingParser.parseJsonFile(JsonTrackingParser.java:362)
    at org.hl7.fhir.igtools.publisher.Publisher.initializeFromJson(Publisher.java:1597)
    ... 3 more

Any ideas?
Source code: https://github.com/HL7/fhir-mCODE-ig/tree/prerelease2
Build log: http://build.fhir.org/ig/HL7/fhir-mCODE-ig/branches/prerelease2/build.log

view this post on Zulip Lloyd McKenzie (Jan 30 2020 at 02:53):

It's not finding an ini file (required for the new template) and so it's looking for an ig.json file and not finding one.

view this post on Zulip Lloyd McKenzie (Jan 30 2020 at 02:53):

And looking at your source, it appears the ini file is indeed missing.

view this post on Zulip Lloyd McKenzie (Jan 30 2020 at 02:54):

Note that the change to the template doesn't remove the need for the ini - still needs to point to the IG and the template and indicate if you're willing to provide feedback. It's just all of the other parameters that have moved.

view this post on Zulip Chris Moesel (Jan 30 2020 at 02:55):

Doh. My fault. I copied parts of the SDC IG .gitignore since they are also on the template and it looks like it gitignored ig.ini. Oops.

view this post on Zulip Lloyd McKenzie (Jan 30 2020 at 02:55):

@Grahame Grieve Any particular reason why usage-stats-opt-out is in the ini file rather than the IG?

view this post on Zulip Chris Moesel (Jan 30 2020 at 02:58):

Actually, no, I take that back. SDC doesn't have it in their .gitignore. That must have been in there from our master branch which wasn't using the new template-based publisher. Sorry for the confusion and thanks for the tip.

view this post on Zulip Lloyd McKenzie (Jan 30 2020 at 02:59):

I'll change the logic so it spits out a slightly nicer error message in a future version of the publisher.

view this post on Zulip Grahame Grieve (Jan 30 2020 at 04:41):

usage-stats-opt-out

view this post on Zulip Grahame Grieve (Jan 30 2020 at 04:41):

I'm not sure

view this post on Zulip Nathan Davis (Aug 25 2021 at 22:14):

Why am I getting these errors? And how do I fix them?

Sushi: error Skipping Extension: an Extension named CertaintyOfPresence already exists. (00:00.0878)
Sushi: File: /scratch/ig-build-temp-GM075P/repo/input/fsh/COVID19Symptoms.fsh    (00:00.0878)
Sushi: Line: 11 - 16                                                             (00:00.0878)
Sushi: error Skipping Extension: an Extension named CertaintyOfAbsence already exists. (00:00.0879)
Sushi: File: /scratch/ig-build-temp-GM075P/repo/input/fsh/COVID19Symptoms.fsh    (00:00.0879)
Sushi: Line: 27 - 32                                                             (00:00.0880)

The build works just fine locally.

view this post on Zulip Melva Peters (Aug 25 2021 at 22:15):

@Lloyd McKenzie

view this post on Zulip Elliot Silver (Aug 25 2021 at 22:15):

This is probably better answered on the #shorthand stream.

view this post on Zulip Grahame Grieve (Aug 25 2021 at 22:24):

why don't you just use the output from the published specification?

view this post on Zulip Grahame Grieve (Aug 25 2021 at 22:25):

I don't really understand why you need to feed a snapshot in, but if you're going to do that, use the right one, which is the one that the publisher generates, not something else

view this post on Zulip Jean Duteau (Aug 25 2021 at 22:25):

it's because you have the extension defined in COVID19Diagnosis and COVID19Symptoms

view this post on Zulip Jean Duteau (Aug 25 2021 at 22:26):

@Grahame Grieve i think your two messages were meant for my topic and not this one

view this post on Zulip Grahame Grieve (Aug 25 2021 at 22:26):

oops. @Jean Duteau yes you're right

view this post on Zulip Chris Moesel (Aug 25 2021 at 22:26):

@Nathan Davis -- As Elliott suggested, #shorthand is a better place for that question (for future reference), but... I can answer you here. You're receiving those errors because you have defined the same extension multiple times in your IG. For example:

It's a similar story for CertaintyOfAbsense.

view this post on Zulip Chris Moesel (Aug 25 2021 at 22:28):

Oops. I see @Jean Duteau beat me to the punch. But I included links. ;-)

view this post on Zulip Nathan Davis (Aug 25 2021 at 22:49):

Weird that I don't see the error when I build locally. Thanks!

view this post on Zulip Nathan Davis (Aug 25 2021 at 23:37):

Weird that I don't see the error when I build locally. Thanks!

view this post on Zulip John Moehrke (Aug 26 2021 at 00:25):

this is brand new sushi

view this post on Zulip John Moehrke (Aug 26 2021 at 00:25):

this afternoon

view this post on Zulip John Moehrke (Aug 26 2021 at 00:25):

don't eat that old sushi


Last updated: Apr 12 2022 at 19:14 UTC