-
Notifications
You must be signed in to change notification settings - Fork 1
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
Warnings and Errors in liboscal-java Throw Exceptions and Crash Catalog Editing in REST Mode #140
Comments
@xee5ch thank you for submitting an issue! Do you have an example catalog that crashes? I tried to replicate that crash using the usnistgov rev 5 catatlog and could not make it crash with Warnings and Errors. I do feel like I have seen this happen before though... |
@tuckerzp The sample is the second collapsed details block. I pulled the latest container from ghcr.io and re ran with the official Rev 5 catalog from NIST and cut more and more until the errors didn't show. That's how I got to that example. That does work. That is very small but the official SP 800-53 Rev 5 has a massive amount of cross-reffed links from back matter so once I got it to one control it worked. I removed bc the constraint warnings are errors in code and exception throwing theory I had. I'll open another report for the UI but separate of this the UI throws an error that there is no back-matter and the resources is an empty array. So I added one resource back! Haha. I'm on mobile now but I'll report that too when I have time tonight. Do you want the example in the report as a gist would that be easier? |
Yeah, that would be great! It will be easier to look into if I can make it crash on my machine. I will try to look into this more to figure out why it is crashing. |
Yeah, we have seen this before. It was way worse in v1.0.4.1 of liboscal-java and that seemed to be due to over-eager error throwing on constraint validation. I think v0.9.0 of metaschema fixed that (and therefore Now we're seeing a weird issue with reflection down in the
The odd thing here is that it seems to be highly inconsistent and transient for a specific failure. I have failed to reproduce a minimal example that fails every time. I think this is at a minimum related to #111 but it very well could be exactly the same thing. @tuckerzp Thank you for taking on the investigation into this; I think that primarily we're going to need to find a path to reliably reproducing this issue to find so we can open an issue on (or make a PR to) |
Interesting, has anyone filed this upstream with David Waltermire and the NIST team? I don't mind helping there.
I don't want help finding a Metaschema repro for this, @tuckerzp or @kylelaker? And as for managing this bug, I don't mind linking or closing and marking this as dupe to focus on that. |
Not yet -- I think we were hoping to actually find a cause and to make sure we're not doing something silly on our end first. And frankly, this issue has sorta slipped my mind. We did eagerly adopt 1.0.4.2 almost purely with the intention of seeing whether this was still an issue.
If you're able to provide any guidance here, we'd certainly appreciate it! Especially when it comes to peeling away the
I think we'll keep them both open for now. Since this one is actually having a conversation, we might just keep this issue around and close #111 later. |
Hi, big fan of your tools. I was experimenting with this tool recently in the oscal-editor-deployment all in one utility with latest. I get the following errors:
Fullish stack trace
It seems you're using the most current liboscal-java, so I assume this is an ongoing issue. I am not sure this is a dupe of #111 or another issue altogether. I do recall reports of, in oscal-cli (and I am not sure this bubbles up from liboscal-java):
WARNING
messages at one time said as much might have been returned as errors when wrapped in a CLI context, not just warnings. Could this explain the stack trace and issues with validations crashing the whole thing? I got it to stop crashing once I slimmed down a catalog I wanted to edit in REST Mode to the bare essentials like so. So, no constraint warnings, no crashes!Not sure how that helps or how to report that bug to NIST and liboscal-java though.
Example Catalog Shaved Down Until Successful
The text was updated successfully, but these errors were encountered: