You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PDS Validate Tool Report
Configuration:
Version 1.15.0
Date 2019-07-23T19:55:43Z
Core Schemas [PDS4_PDS_1C00.xsd]
Core Schematrons [PDS4_PDS_1C00.sch]
Model Version 1C00
Parameters:
Targets [file:/Users/jpadams/Downloads/manifests_ladee_mission_bundle_20190717/ladee_mission_bundle_SIP_4col_manifest_v1.0.xml]
Severity Level WARNING
Recurse Directories true
File Filters Used [*.xml, *.XML]
Force Mode off
Data Content Validation on
Max Errors 100000
Registered Contexts File /Users/jpadams/Downloads/validate-1.15.0/resources/registered_context_products.json
Product Level Validation Results
FAIL: file:/Users/jpadams/Downloads/manifests_ladee_mission_bundle_20190717/ladee_mission_bundle_SIP_4col_manifest_v1.0.xml
Begin Content Validation: file:/Users/jpadams/Downloads/manifests_ladee_mission_bundle_20190717/ladee_mission_bundle_SIP_4col_manifest_v1.0.tab
ERROR [error.table.record_length_mismatch] table 1, record 1: Record length exceeds the max defined record length (expected 59, got 156).
ERROR [error.table.record_length_mismatch] table 1, record 2: Record length exceeds the max defined record length (expected 59, got 185).
ERROR [error.table.record_length_mismatch] table 1, record 3: Record length exceeds the max defined record length (expected 59, got 195).
ERROR [error.table.record_length_mismatch] table 1, record 4: Record length exceeds the max defined record length (expected 59, got 188).
ERROR [error.table.record_length_mismatch] table 1, record 5: Record length exceeds the max defined record length (expected 59, got 198).
ERROR [error.table.record_length_mismatch] table 1, record 6: Record length exceeds the max defined record length (expected 59, got 184).
ERROR [error.table.record_length_mismatch] table 1, record 7: Record length exceeds the max defined record length (expected 59, got 184).
ERROR [error.table.record_length_mismatch] table 1, record 8: Record length exceeds the max defined record length (expected 59, got 190).
ERROR [error.table.record_length_mismatch] table 1, record 9: Record length exceeds the max defined record length (expected 59, got 190).
ERROR [error.table.record_length_mismatch] table 1, record 10: Record length exceeds the max defined record length (expected 59, got 194).
ERROR [error.table.record_length_mismatch] table 1, record 11: Record length exceeds the max defined record length (expected 59, got 204).
ERROR [error.table.record_length_mismatch] table 1, record 12: Record length exceeds the max defined record length (expected 59, got 175).
ERROR [error.table.record_length_mismatch] table 1, record 13: Record length exceeds the max defined record length (expected 59, got 175).
End Content Validation: file:/Users/jpadams/Downloads/manifests_ladee_mission_bundle_20190717/ladee_mission_bundle_SIP_4col_manifest_v1.0.tab
Summary:
13 error(s)
0 warning(s)
Message Types:
13 error.table.record_length_mismatch
End of Report
Previous solution would not allow validate to properly use methods that depended on VICAR. This method appears to work properly after testing.
Refs NASA-PDS/validate#55
Bug is fixed in PDS4-JParser and the way it handles the VICAR dependency. No idea why the software wasn't catching the error, but I couldn't seem to track down the reason why it was failing validation but no errors were thrown. Punting that down the road in the event another issue arises.
Describe the bug
Ever since ceb1dda it appears that content validation no longer works (at least for table data).
To Reproduce
Run validate with current version on attached XML (be sure to change filename to .xml instead of .xml.txt):
Expected behavior
Ran with validate-1.15.0 (last working version I was able to test was fa57004)
Which gives the following output:
ladee_mission_bundle_SIP_4col_manifest_v1.0.xml.txt
ladee_mission_bundle_SIP_4col_manifest_v1.0.tab.txt
The text was updated successfully, but these errors were encountered: