Merge V2.2 backports to fix F10.7 index update scripting #119
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also updated RamIndices file to reflect recent changes
- Use SSLContext to avoid bad certification check on RHEL - Update RamIndices.txt
Rebuilding the image was failing due to pip/python changes. The pip update fixes that. New SpacePy was grabbed for QoL updates.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Index update broke on CCMC build due to NRCan's F10.7 server changing location and protocol. This PR addresses that (Closes #117)
Update captures some changes:
updateRamIndices.pynow fetches from there using the new protocolRamIndices.txtfile updated to reflect recent dataDockerfile.RoRupdated to fix rebuild issue withpip