-
Notifications
You must be signed in to change notification settings - Fork 11
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
Fix uncaught exception error when validating an array object #155
Comments
This issue was also discussed by email with @jordanpadams and @jshughes416 - possibly a two-part solution technical solution was needed, i.e. updated Schematron rule in the core dictionary to check the number instances of <Axis_Array> against and also address the error in validate. But the proposal was also made to re-visit allowing Array_1D rather than using the generic array class... |
@fran-vallejo would you mind attaching an example product for testing? |
@jordanpadams As we detected this problem validating a preliminary Bepi product that the user would prefer not to make public yet, I'll send you a copy by mail. |
As well as @fran-vallejo's email, find attached a test product which demonstrates the issue: which gives:
|
Note: this issue does not appear related to the memory footprint issue |
implementation per #543 now throws a "bad_file_read" error. |
Describe the bug
validate raises an exception while validating a product.
As the product is invalid, I expect a message indicating what the problem is instead of one indicating there has been an uncaught exception.
The problem with the product is there is an inconsistency between the number of axes declared and the number of axes defined for an array object.
The declared value for Array>axes is 2, but then only one Array>Axis_Array entity has been defined.Changing the axes value from 2 to 1 the exception messages disappear.
To Reproduce
@msbentley will send / attach the product.
Expected behavior
As the product is invalid, a proper message indicating what the problem is instead of one indicating there has been an uncaught exception.
Version of Software Used
PDS Validate Tool Report
Configuration:
Version 1.17.5
Date 2019-11-19T10:01:35Z
...
Product Level Validation Results
PASS: gov.nasa.pds.validate.ValidateLauncher
WARNING [warning.product_not_registered] Non-registered context products should only be used during archive development. All context products must be registered for a valid, released archive bundle.
FAIL: file:/home/fvallejo/TestData/strofio/srn_raw_strofio_re-hq-tof_20190405_20190406.xml
ERROR [error.validation.internal_error] Uncaught exception while validating: null
FAIL: file:/home/fvallejo/TestData/strofio/srn_raw_strofio_re-lq-tof_20190405_20190406.xml
ERROR [error.validation.internal_error] Uncaught exception while validating: null
Validation complete.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: