Open aj-stein-nist opened 1 year ago
So it appears the assertion that a control lookup in the index during flattening is the cause of the exception. When stepping through with a debugger, the control in question is control-2
because it is not included from the profile and dropped, so it is not included within the index.
Describe the bug
While writing tests for usnistgov/oscal-cli#178, I have been unable to resolve a profile with a catalog with a "flat" catalog that has only two controls. This is using a development version using liboscal-java v3.0.2 as a dependency.
Catalog that throws stack trace:
Catalog that does not throw stack trace:
Profile:
Stack trace:
Who is the bug affecting?
What is affected by this bug?
Profile resolution with catalogs that do not have groups.
When does this occur?
Consistently.
How do we replicate the issue?
Review the examples or use the integration tests in in the 178-add-integration-tests branch.
See the above stack trace for further details.
Expected behavior (i.e. solution)
The catalog resolves correctly if it does not have groups.
Other Comments
N/A