Stream: IG creation
Topic: new error with publisher 1.1.74
Jose Costa Teixeira (Jun 17 2021 at 22:03):
Since 1.1.74 (a few hours ago), I'm getting a new error that I cannot figure out what's missing.
This is the error:
Generating Narratives (01:22.0648)
Publishing Content Failed: null (01:25.0499)
(01:25.0551)
Use -? to get command line help (01:25.0586)
(01:25.0600)
Stack Dump (for debugging): (01:25.0604)
java.lang.NullPointerException
at org.hl7.fhir.r5.context.BaseWorkerContext.getLinkForUrl(BaseWorkerContext.java:1895)
at org.hl7.fhir.r5.renderers.QuestionnaireRenderer.renderItemOptions(QuestionnaireRenderer.java:135)
at org.hl7.fhir.r5.renderers.QuestionnaireRenderer.renderOptions(QuestionnaireRenderer.java:107)
at org.hl7.fhir.r5.renderers.QuestionnaireRenderer.renderOptions(QuestionnaireRenderer.java:108)
at org.hl7.fhir.r5.renderers.QuestionnaireRenderer.renderOptions(QuestionnaireRenderer.java:108)
at org.hl7.fhir.r5.renderers.QuestionnaireRenderer.renderOptions(QuestionnaireRenderer.java:108)
at org.hl7.fhir.r5.renderers.QuestionnaireRenderer.renderOptions(QuestionnaireRenderer.java:101)
at org.hl7.fhir.r5.renderers.QuestionnaireRenderer.renderTree(QuestionnaireRenderer.java:92)
at org.hl7.fhir.r5.renderers.QuestionnaireRenderer.render(QuestionnaireRenderer.java:56)
at org.hl7.fhir.r5.renderers.QuestionnaireRenderer.render(QuestionnaireRenderer.java:47)
at org.hl7.fhir.r5.renderers.ResourceRenderer.render(ResourceRenderer.java:74)
at org.hl7.fhir.igtools.publisher.Publisher.generateNarratives(Publisher.java:1155)
at org.hl7.fhir.igtools.publisher.Publisher.loadConformance(Publisher.java:3907)
at org.hl7.fhir.igtools.publisher.Publisher.createIg(Publisher.java:889)
at org.hl7.fhir.igtools.publisher.Publisher.execute(Publisher.java:744)
at org.hl7.fhir.igtools.publisher.Publisher.main(Publisher.java:8559)
Jose Costa Teixeira (Jun 17 2021 at 22:06):
is there a way to figure out what's the offending content? I tried to remove a few things from the questionnaire, and I think it behaves better when I remove the .answerOption.valueCodings in the questionnaire
Jose Costa Teixeira (Jun 17 2021 at 22:07):
@Grahame Grieve is this known? Any ideas (sorry for ping, maybe a fix is on the way, it's just that it broke the build and perhaps there is some new checks for errors that I ignored before)
Grahame Grieve (Jun 17 2021 at 22:10):
you have an answerOption coding without a system?
Jose Costa Teixeira (Jun 17 2021 at 23:02):
yes, I do. is that the issue?
Jose Costa Teixeira (Jun 17 2021 at 23:02):
some answeroptions are yes/no, do we need a system for that?
Jose Costa Teixeira (Jun 17 2021 at 23:03):
more "yes, no, maybe" - otherwise I'd just use a boolean of course
Grahame Grieve (Jun 17 2021 at 23:19):
well, I overlooked that possibility. So it won't build like that for now. Release after the one currently in the pipeline will fix that
As for whether you should have a system for that.. I think you should, but that's a subject for #questionnaire
Jose Costa Teixeira (Jun 17 2021 at 23:45):
ok I just cheated (using one codesystem for all the answeroptions in the questionnaire) and I confirm that fixes it. Thanks!
Last updated: Apr 12 2022 at 19:14 UTC