-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NPE when resolving profile selecting catalog children controls without parent #232
Comments
I have investigated this further but I need to review the current profile resolution specification and debug further with additional test cases locally. That said, given the additional reports of usnistgov/OSCAL#1662 and usnistgov/OSCAL#1663, I might need to be straightened out to know what should change here, and what should change in XSLT, and what is correct after re-reading the specification. Thanks again for this report. |
I will be out on leave next week but will keep this assigned for the time being. If others clear the sprint board rapidly, they can feel free to pick this up. |
First off, I need to transfer this issue where applicable, the core liboscal-java library, not the CLI repo itself where it currently is. I am assessing the viability of fixing this for an upcoming patch release or later after I transfer the issue. More to follow. |
This may be a business logic error or perhaps at one time there was/is a valid reason, but as it stands the BasicIndexer would detect unselected controls for resolution of the profile but only drop them when their parent was selected for the default strategy of flattening. For simple trees where c1 is the root control and c1.1 is the child, so c1 -> c1.1, c1 was not being correctly removed. NOTE: Logging indicates a double index of c1.1 even with this change so that still needs to be fixed most likely to resolve this issue.
This may be a business logic error or perhaps at one time there was/is a valid reason, but as it stands the BasicIndexer would detect unselected controls for resolution of the profile but only drop them when their parent was selected for the default strategy of flattening. For simple trees where c1 is the root control and c1.1 is the child, so c1 -> c1.1, c1 was not being correctly removed. NOTE: Logging indicates a double index of c1.1 even with this change so that still needs to be fixed most likely to resolve this issue.
Describe the bug
oscal-cli
throwsException in thread "main" java.lang.NullPointerException
when resolving a profile.Who is the bug affecting?
Users of
oscal-cli
who wish to resolve a profile.What is affected by this bug?
oscal-cli
fails during execution.When does this occur?
macOS Ventura 13.2.1 MacBook Pro Intel hardware.
How do we replicate the issue?
Build
oscal-cli
usingmain
branch of cloned repo.Create an OSCAL profile instance document.
Create an OSCAL catalog instance document.
Perform a profile resolution. Receive exception.
Expected behavior (i.e. solution)
A resolved profile catalog document should be produced.
Other Comments
The specimen instance documents are in the attached archive.
c-ce.zip
The text was updated successfully, but these errors were encountered: