-
Notifications
You must be signed in to change notification settings - Fork 501
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
[Bug] Fix bug in version_lock.py #1880
[Bug] Fix bug in version_lock.py #1880
Conversation
name = current_rule_lock['rule_name'] | ||
existing_type = current_rule_lock['type'] | ||
existing_type = existing_rule_lock['type'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was referencing the new lock info rather than the existing (lock file) lock info as expected
@@ -70,8 +70,8 @@ def manage_versions(self, rules: RuleCollection, | |||
"""Update the contents of the version.lock file and optionally save changes.""" | |||
from .packaging import current_stack_version | |||
|
|||
current_version_lock = deepcopy(self.version_lock) | |||
version_lock_hash = dict_hash(current_version_lock) | |||
lock_file_contents = deepcopy(self.version_lock) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this refactor is just for more clarity in the code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. LGTM
(cherry picked from commit 17ef6c5)
(cherry picked from commit 17ef6c5)
(cherry picked from commit 17ef6c5)
(cherry picked from commit 17ef6c5)
(cherry picked from commit 17ef6c5)
(cherry picked from commit 17ef6c5)
Issues
None
Summary
Noticed this didn't cause an expected failure when reviewing another PR, and found a small bug where the wrong lock was referenced