Check the compatibility of cached analysis.json with what is the passed as an argument.
#136
Conversation
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
rahlk
changed the title
analysis.json with what is the passed as an argument.
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.
When the user passes a new analysis level for CLDK, but an analysis.json artifact exisits in the cache, the python API ignores the user's upgraded request for a deeper analysis level.
Motivation and Context
This change ensures the the
analysis.jsoncache has be updated upon the user's new request for a different analysis level.How Has This Been Tested?
All the existing test cases pass.
Breaking Changes
No
Types of changes
Checklist
Additional context