-
Notifications
You must be signed in to change notification settings - Fork 12
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
Confusing error message when running with multiple IM's in local schematron #958
Comments
@rgdeen we got your ticket. we will add it to the backlog. |
Okay so further investigation... something is wrong with the 1M00 schematron. If I use it alone (even renamed to 1G to match the others), I get the above error. So it's not about having multiple versions... it's about having a bad schematron file. So validate should somehow at least report which file it's trying to read when this kind of error occurs. It would be okay if it just did this with verbose=1 for debugging purposes (like, maybe even always report "reading schematron xxx" in verbose mode?). The error is referring to mars2020 somehow which has nothing to do with the msn ldd, which is what makes it so hard to find. I'll submit a ticket on the msn ldd itself. |
@rgdeen FYI, I updated your original ticket to format the validate execution to properly document how it was run |
@rgdeen looks like this may be an issue with your CLI execution with local schemas/schematrons. It checks out when you load from the internet:
|
Checked for duplicates
No - I haven't checked
🐛 Describe the bug
Running with local xsd/sch files, somehow we ended up with two versions of PDS4_MSN: PDS4_MSN_1G00_1300 and PDS4_MSN_1M00_1303.
This is clearly an error, but the error message was unhelpful and it took a couple hours to figure out the problem.
Notice the "Error near" messages that come out before the product validation, with references to xsl templates that are not visible to the user. And the error "Namespace prefix 'mars2020' has not been declared" is actually wrong... the namespace has been declared.
🕵️ Expected behavior
This situation is clearly a bug and I'm happy with validate failing. But the error message could be a lot more helpful.
📜 To Reproduce
Including a tarball below with sample image and the set of LDDs. Extract it and then:
🖥 Environment Info
Did the same thing on both linux and Mac
📚 Version of Software Used
did the same thing on both validate 3.4.1 and 3.5.1
🩺 Test Data / Additional context
junk.tar.gz
🦄 Related requirements
🦄 #xyz
⚙️ Engineering Details
No response
🎉 Integration & Test
No response
The text was updated successfully, but these errors were encountered: