-
Notifications
You must be signed in to change notification settings - Fork 710
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
Fix consumer handling in pallet balances update_locks
#1970
Comments
Self-assigned, I need to spend some time understanding this for writing docs anyway. |
we need a script to check if this bug have happened on any parachain and generate a list of accounts that needs fix up |
and this is something should be identified by a fuzzer so I guess we don’t have enough of them |
I can image it could be hard to write such script that works on all the parachains. That should spark another question: What can we improve to make such task easier in future? e.g. better event system or better indexer or better invariant checker |
Writing a script for every chain should be possible. You just need to monitor |
@bkchr Does this relate to this issue? #1404 (comment) |
Could probably be related. |
…ng consumers (paritytech#1976) Closes paritytech#1970 Follow up issue to tackle, once the erroneous double incrementing/decrementing has stopped: paritytech#2037
…ng consumers (paritytech#1976) Closes paritytech#1970 Follow up issue to tackle, once the erroneous double incrementing/decrementing has stopped: paritytech#2037
When removing all locks of an account there is a bug that leads to reducing the consumer count twice.
First it happens here:
polkadot-sdk/substrate/frame/balances/src/lib.rs
Line 969 in f0ab54e
And then the second time here:
polkadot-sdk/substrate/frame/balances/src/lib.rs
Line 1072 in f0ab54e
The text was updated successfully, but these errors were encountered: