-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
track delegation vesting accounts #8946
track delegation vesting accounts #8946
Conversation
* during migration, reset corrupted values to zero
This pull request introduces 2 alerts and fixes 2 when merging 80335ad into c0cb1d2 - view on LGTM.com new alerts:
fixed alerts:
|
This pull request fixes 2 alerts when merging 9a1c74a into c0cb1d2 - view on LGTM.com fixed alerts:
|
This pull request fixes 2 alerts when merging 93b2ec9 into c0cb1d2 - view on LGTM.com fixed alerts:
|
This pull request fixes 2 alerts when merging c10b189 into c0cb1d2 - view on LGTM.com fixed alerts:
|
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.
Looks reasonable to me. Any reason this is preferred over the original approach? Is the original approach broken?
This PR adds a more general test case and a clearing pass in the migration. Not a completely new approach, but a rather important factor that was missing in #8865, hence the PR-on-PR :D |
Small change to the previous approach - zero-out the fields and don't clamp down the delegation amount before calling |
I am merging this, looks fine and adds further refinements to the migration code. |
@gsora @alexanderbez what do you guys think of this patch to the account migration?
TrackDelegation
SetAccount
😅