Stream: committers
Topic: Error:Null on build
David Pyke (Mar 11 2022 at 15:16):
I committed changes to Consent and ran a push (which works locally) and got this:
2022-03-11T14:41:10.1530495Z Candidate for CodeableReference: [ClinicalImpression.prognosis]
2022-03-11T14:41:10.4530536Z This was a Full Build 1.18 36sec 4956MB
2022-03-11T14:41:10.5530140Z FHIR build failure @ Fri, Mar 11, 2022 14:41+0000 0.109 36sec 4956MB
2022-03-11T14:41:10.5531468Z Error: null
2022-03-11T14:41:10.5533191Z java.lang.NullPointerException
2022-03-11T14:41:10.5534377Z at java.util.ResourceBundle.containsKey(ResourceBundle.java:1821)
2022-03-11T14:41:10.5535441Z at org.hl7.fhir.utilities.i18n.I18nBase.messageExistsForLocale(I18nBase.java:50)
2022-03-11T14:41:10.5536610Z at org.hl7.fhir.utilities.i18n.I18nBase.formatMessage(I18nBase.java:67)
2022-03-11T14:41:10.5538091Z at org.hl7.fhir.validation.BaseValidator.ruleHtml(BaseValidator.java:427)
2022-03-11T14:41:10.5539190Z at org.hl7.fhir.definitions.validation.ResourceValidator.rule(ResourceValidator.java:124)
2022-03-11T14:41:10.5540363Z at org.hl7.fhir.definitions.validation.ResourceValidator.checkSearchParams(ResourceValidator.java:383)
2022-03-11T14:41:10.5541525Z at org.hl7.fhir.definitions.validation.ResourceValidator.check(ResourceValidator.java:217)
2022-03-11T14:41:10.5543059Z at org.hl7.fhir.definitions.validation.ResourceValidator.check(ResourceValidator.java:594)
2022-03-11T14:41:10.5544182Z at org.hl7.fhir.tools.publisher.Publisher.validate(Publisher.java:1886)
2022-03-11T14:41:10.5545175Z at org.hl7.fhir.tools.publisher.Publisher.execute(Publisher.java:702)
2022-03-11T14:41:10.5546183Z at org.hl7.fhir.tools.publisher.Publisher.main(Publisher.java:487)
David Pyke (Mar 11 2022 at 15:17):
What should I do?
David Pyke (Mar 11 2022 at 15:17):
David Pyke (Mar 11 2022 at 15:29):
@Mark Iantorno @Grahame Grieve ?
John Moehrke (Mar 11 2022 at 15:52):
well, you have many warnings, and warnings can't be there if you want FMM3
David Pyke (Mar 11 2022 at 15:53):
Thank you, but that doesn't fix the error
John Moehrke (Mar 11 2022 at 15:53):
are you sure? I was getting this same crazy error yesterday until I eliminated by build warnings
David Pyke (Mar 11 2022 at 15:54):
It's a null pointer exception. That's a flaw in the publisher code.
John Moehrke (Mar 11 2022 at 15:55):
you are thinking that the final failure is not caused by the well handled warnings?
John Moehrke (Mar 11 2022 at 15:57):
no question the build should handle this better
ERROR @ Consent: Cannot invoke "org.hl7.fhir.definitions.model.ElementDefn.getTypes()" because "e" is null (src = ResourceValidator)
David Pyke (Mar 11 2022 at 16:00):
Can you have a look at the code and see if you can find the bug? I'm sure they'd appreciate the extra eyes
Lloyd McKenzie (Mar 11 2022 at 16:54):
The error is actually being caused by a validation rule being fired - so yes, getting rid of all validation issues would get rid of the problem (if you could figure out what the validation issue was that was triggering the problem). However, this is definitely a publisher bug that needs to be fixed.
Lloyd McKenzie (Mar 11 2022 at 18:07):
I looked at the code and it indicates that something really funky is going on inside ResourceBundle, which is Java internal stuff. The cause seems to be that an exception is being triggered when running SearchParameter validation logic on SearchParameters with type 'Reference' or 'uri' and the message being passed into the rules engine is the exception message - which doesn't have a translation and the translation process is then choking. @Mark Iantorno will need to chase why. (Hopefully knowing the type of search parameter that's causing the problem will help you narrow down the issue .
Mark Iantorno (Mar 11 2022 at 19:49):
@David Otasek
Mark Iantorno (Mar 11 2022 at 19:49):
David will look into this.
David Otasek (Mar 11 2022 at 21:22):
@Mark Iantorno @David Pyke Looking into it.
David Otasek (Mar 11 2022 at 22:08):
@David Pyke It looks like the root cause of this is the search parameterConsent.policy.uri
This element doesn't appear to exist. Here's a screenshot of elements that DO exist when the publisher reaches this point:
Screen-Shot-2022-03-11-at-5.05.54-PM.png
Lloyd McKenzie (Mar 11 2022 at 23:33):
Do we understand why we get an NPE rather than a useful message?
David Otasek (Mar 11 2022 at 23:51):
@Lloyd McKenzie yes. I'm in the process of adding a better message now, but am having some odd IDE difficulties trying to test my changes.
David Pyke (Mar 12 2022 at 14:32):
Thanks! I've fixed it.
Last updated: Apr 12 2022 at 19:14 UTC