You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
balance_waitgroup's type is uint32 so that it's smallest value will be zero and we don't need to check the value below 0 but if we continue decrease BalanceWaitgroup's when it equal to 0, BalanceWaitgroup's value will = 4294967295 (max uint32)
So we originally had this throw an error if it went below 0, but it can legitimately happen (e.g. if there is a backlog of icq queries that exist from the previous epoch that suddenly get resolved). So it can, and does go below zero, although a review of these cases and checking to see if there is a better way to resolve them would be a good point of investigation.
This is something that batched queries might go some way to resolving also.
Summary of Bug
balance_waitgroup
's type is uint32 so that it's smallest value will be zero and we don't need to check the value below 0 but if we continue decreaseBalanceWaitgroup
's when it equal to 0,BalanceWaitgroup
's value will = 4294967295 (max uint32)quicksilver/x/interchainstaking/types/accounts.go
Lines 39 to 40 in ba00077
Expected Behaviour
Discuss in case
BalanceWaitgroup
= 0 and we keep decreasing it and update the statelessSteps to Reproduce
For Admin Use
The text was updated successfully, but these errors were encountered: