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
A bug happened!
When you revoke an allowance in order to create a new one with a later expiration time. The queue entity for the allowance still exists in the expiration queue. Which leads to situation whec the allowance removed unexpectedly due to outdated queue entity in the endblocker.
The bug in not reproducible with sdk.0.50, because queue entity is cleared as well during revoke method.
It's possible to fix it the same way in sdk0.47
Cosmos SDK Version
0.47
How to reproduce?
grant allowance with expiration date = date1
revoke allowance
grant allowance for the same granter + grantee with expiration date = date2
check that expiration queue contains two records
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
What happened?
A bug happened!
When you revoke an allowance in order to create a new one with a later expiration time. The queue entity for the allowance still exists in the expiration queue. Which leads to situation whec the allowance removed unexpectedly due to outdated queue entity in the endblocker.
The bug in not reproducible with sdk.0.50, because queue entity is cleared as well during revoke method.
It's possible to fix it the same way in sdk0.47
Cosmos SDK Version
0.47
How to reproduce?
grant allowance with expiration date =
date1
revoke allowance
grant allowance for the same granter + grantee with expiration date =
date2
check that expiration queue contains two records
The text was updated successfully, but these errors were encountered: