Use snapshot archive if last snapshot is corrupt #91
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Use snapshot archive if last snapshot is corrupt.
In simulated local testing this fixes the issue recently experienced where the last snapshot at /data/mta4/www/Snapshot/chandra.snapshot is truncated and doesn't have an obsid.
Interface impacts
The code uses the archived snapshots in reverse time order if the last file snapshot is corrupt. Practically this is not an interface inpact but the snapshot time could be even older while the replan central page is still up-to-date.
Functional testing
For local testing, I just deleted the obsid value in the parsed snapshot right in the code and confirmed that the code went into the archive loop and got a new snapshot.
Practically, I do not have a way to test this in the real situation of the snapshot being broken as I'm not really sure what will be found in the snapshot archive at that time. But the change seems benign.