-
Notifications
You must be signed in to change notification settings - Fork 4
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
A expect constraint with id 'metaschema-deprecated-types', matching the item at path '/metaschema-meta-constraints', resulted in an unexpected error. #350
Comments
I think this is an instance of #323, which has been fixed. I don't think the liboscal-java and oscal-cli has been advanced to use the latest m-j to get this fix. |
ok glad to hear it! |
I was wondering why I couldn't find this earlier today. I just noticed it was in the metaschema spec and docs/website repo, not the Java implementation repo. Transferring it now just to reduce confusion (I was like where is the Java build after clicking in the web interface here and reading GitHub Action configs 😆). |
Is this now fixed? |
I am rebuilding current SNAPSHOTs from |
I tested with a local build with the following details and I was unable to reproduce the exception. % oscal-cli version
oscal-cli 2.5.0-SNAPSHOT built at 2025-02-27 19:16 from branch develop (ba14f61) at Unknown
liboscal-java 5.2.0-SNAPSHOT built at 2025-02-27 19:06 from branch develop (0d8fbdb) at Unknown
oscal v1.1.3 built at 2025-02-27 19:06 from branch b39789e5ab6df36dbe14f481e40113b91fd25f3f (b39789e) at https://github.com/usnistgov/OSCAL.git
metaschema-java 2.2.0-SNAPSHOT built at 2025-02-27T17:56:27+0000 from branch 284-date-time-extraction-functions (e837c3c) at Unknown
metaschema 2.2.0-SNAPSHOT built at 2025-02-27T17:56:27+0000 from branch 7e49638c1ad19fadc0e556cfca90478f3aae9489 (7e49638) at https://github.com/metaschema-framework/metaschema.git
% curl -L -O https://raw.githubusercontent.com/metaschema-framework/metaschema/3d78ec188f4ccf4cba63f820fc89ff77130e05ed/schema/metaschema/metaschema-module-constraints.xml
% oscal-cli metaschema validate-content -m /home/me/metaschema/schema/metaschema/metaschema-module-metaschema.xml /home/me/oscal/src/metaschema/oscal_complete_metaschema.xml -c metaschema-module-constraints.xml
Loading 'file:/private/tmp/mj350_test/metaschema-module-constraints.xml'
Validating 'file:/home/me/oscal/src/metaschema/oscal_complete_metaschema.xml' as XML.
Loading 'file:/home/me/metaschema/schema/metaschema/metaschema-module-metaschema.xml'
Generating Java classes in: /var/folders/_q/y32s9yw56lb81l1sjgtp7k080000gn/T/metaschema-cli-12729131819974803051
Replacing matcher for QName: Q{http://csrc.nist.gov/ns/oscal/metaschema/1.0}METASCHEMA-CONSTRAINTS
Replacing matcher for QName: Q{http://csrc.nist.gov/ns/oscal/metaschema/1.0}metaschema-meta-constraints
Replacing matcher for QName: Q{http://csrc.nist.gov/ns/oscal/metaschema/1.0}METASCHEMA
The file 'file:/home/me/oscal/src/metaschema/oscal_complete_metaschema.xml' is valid. |
https://github.com/metaschema-framework/metaschema/blob/3d78ec188f4ccf4cba63f820fc89ff77130e05ed/schema/metaschema/metaschema-module-constraints.xml#L57
this constraint is crashing in the new SNAPSHOT instance
https://github.com/GSA/fedramp-automation/actions/runs/12747585931/job/35525952540?pr=1072#step:7:69
not sure why this is happening, and i can't tell if this is a malformed constraint, or if this is a metaschema java bug, just noticing it and marking it here
The text was updated successfully, but these errors were encountered: