-
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
Validate does not maintain history of other versions it comes across as it traverses directories causing erroneous WARNING messages #597
Comments
@al-niessner wrap up your current ticket, and then let's loop back to this and another ticket I am about to create that have introduced a couple regressions |
@jordanpadams @nutjob4life @tloubrieu-jpl Seems like a bad state to be in the icebox and high priority. If one of the two states where to change, which is the correct answer. |
@al-niessner removed the high priority tag |
@al-niessner ☝️ |
@al-niessner note: this is for the legacy file system validate, not registry validator |
@jordanpadams @nutjob4life @tloubrieu-jpl I am getting these fatals:
Can somebody explain what it means and how to fix it? On the naif site referenced in the top of this issue the directories are |
@jordanpadams @nutjob4life @tloubrieu-jpl This problem is more complicated than what the initial statement make it out to be. First, the base bundles are skipped (implied through initial statements validate summary):
Since the old versions are skipped, validate cannot have a memory or have a knowledge of them. To get the knowledge or memory, the past units would have to be processed to include warts and all. The other obvious option is to simply ignore not referenced objects but then it also include objects that are not just previous versions. How do we want to resolve this conundrum as it is politics that will decide the technological? |
@al-niessner understood. I am OK with this:
If possible, I would like us to read in these skipped labels, identify the files associated with it, and ignore those as well. the confusing part is it finds and skips these labels, but then it throws a WARNING on the associated inventory file (CSV):
does that make sense? |
@jordanpadams @nutjob4life @tloubrieu-jpl Ready for review or nearly. It now works as requested but am getting these two errors:
They have nothing to do with this ticket. I do not understand them so cannot correct them. If anyone can tell me what they are and how to correct them, then I can set this up in features for regression testing. Otherwise the code is ready. |
Checked for duplicates
Yes - I have checked
🐛 Describe the bug
Per NASA-PDS/operations#322 (comment) and the validate report denoted in NASA-PDS/operations#322, validate is throwing erroneous WARNING messages for past versions of bundles/collections in the directory used as the target.
🕵️ Expected behavior
Validate would maintain an understanding of past versions of bundles and the past versions of collections they refer to, and simple SKIP validation of those products without throwing a WARNING.
📜 To Reproduce
validate -R pds4.bundle -t /path/to/naif/dataset
🖥 Environment Info
📚 Version of Software Used
v3.1.1
🩺 Test Data / Additional context
https://naif.jpl.nasa.gov/pub/naif/pds/pds4/mars2020/mars2020_spice/
or for a smaller data set:
https://pds.nasa.gov/data/pds4/test-data/custom-datasets/naif3/
🦄 Related requirements
No response
⚙️ Engineering Details
Looks like regression was introduced prior to v3.1.1. Do not see this in v3.0.3
The text was updated successfully, but these errors were encountered: