Supporting manifest file failover#13
Merged
Merged
Conversation
aslisabanci
approved these changes
Nov 19, 2021
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR enables algorithms that do not have a frozen manifest file (manifest_file.json.freeze) to still be executed.
algo freezevia the CLI is the only method to freeze a model, and it's not desirable to constantly keep freezing models during testing and development.This changes makes it so if no .freeze file exists, the model manifest system will skip attempting to compare the md5 hashes between the model and a previously recorded. This allows for the use of the model manifest system, if/when a user or workflow doesn't have the ability to freeze their manifest file with the CLI, or doesn't want to.