Open bwalsh opened 4 years ago
cc @liberaliscomputing
From slack:
Shahim Essaid 12:17 PM Still not sure but the problem appears to be with generating the snapshot for one of the StructureDefinitions. See this this part of the exception stack 12:17 at java.base/java.util.ArrayList.get(ArrayList.java:458) at org.hl7.fhir.r4.conformance.ProfileUtilities.updateFromDefinition(ProfileUtilities.java:1683) at org.hl7.fhir.r4.conformance.ProfileUtilities.processPaths(ProfileUtilities.java:1055) at org.hl7.fhir.r4.conformance.ProfileUtilities.processPaths(ProfileUtilities.java:628) at org.hl7.fhir.r4.conformance.ProfileUtilities.generateSnapshot(ProfileUtilities.java:454) at org.hl7.fhir.common.hapi.validation.support.SnapshotGeneratingValidationSupport.generateSnapshot(SnapshotGeneratingValidationSupport.java:66) at org.hl7.fhir.common.hapi.validation.support.ValidationSupportChain.generateSnapshot(ValidationSupportChain.java:65)
12:18 i'll have to look carefully through the profiles to see what's missing there. check to see if all the paths being referenced, the nesting, etc. is correct. 12:19 i'm guessing there is something wrong with path references to paths that are supposed to exist in the base definition
Walsbr 12:19 PM much appreciated. thank you! (edited)
Shahim Essaid 12:20 PM to help debug this (unless you can do remote JVM debugging) is to gradually build up your instance example to use one extension profile at a time until you hit the problematic one 12:20 otherwise you 12:20 you're not sure which one it is 12:21 so, loosen your cardinality restrictions and then use one nested extension at a time. 12:21 once the profiles are working, go back and reapply your cardinalities 12:22 but carefully double check your paths in your profiles 12:22 one way is to get the base definitions you're using and make sure your paths match something in the base
Describe the Bug
Smile CDR returns a 500 when presented a resource with
nested extension
To Reproduce
Step 1: Add profile and extensions
Profile:
drs-attachment
Extensions
drs-object
drs-checksum
drs-access-method
Step 2: Post an Example Resource
Server Behaviors
Expected Behavior
A 200 or 201 response
Actual Behavior