-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
feat(x/feegrant): Add limits to grant pruning and enable message to aid manually #18047
Conversation
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.
The build is failing because you need to bump the api module in x/feegrant to a commit from this branch. Otherwise, it does not know the rpc.
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.
If we do params I think we need a migration and bump consensus version
im not sure its worth adding this as params, it feels like its something that will never get touched. I think setting it to something like 200 in endblock and 75 in the message is fine. |
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.
one question, otherwise lgtm
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.
can you also fix the failing tests?
Idk what's going on with the CI on this PR, amd64 build fails and tests are failing with race conditions and other weird errors. Locally it looks fine (it works on my machine™) |
…id manually (#18047) (cherry picked from commit 4caecf1) # Conflicts: # client/v2/go.mod # client/v2/go.sum # go.mod # go.sum # simapp/go.mod # simapp/go.sum # simapp/gomod2nix.toml # tests/go.mod # tests/go.sum # tests/starship/tests/go.mod # tests/starship/tests/go.sum # x/circuit/go.mod # x/circuit/go.sum # x/evidence/go.mod # x/evidence/go.sum # x/feegrant/go.mod # x/feegrant/go.sum # x/feegrant/keeper/keeper.go # x/feegrant/keeper/keeper_test.go # x/feegrant/keeper/msg_server_test.go # x/feegrant/module/abci_test.go # x/nft/go.mod # x/nft/go.sum # x/params/go.mod # x/params/go.sum # x/protocolpool/go.mod # x/protocolpool/go.sum # x/upgrade/go.mod # x/upgrade/go.sum
@@ -206,6 +206,14 @@ The feegrant module emits the following events: | |||
| message | granter | {granterAddress} | | |||
| message | grantee | {granteeAddress} | | |||
|
|||
### Prune fee allowances |
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.
The message wasn't added here. Can you make sure to add it
…id manually (backport #18047) (#18128) Co-authored-by: Facundo Medica <[email protected]> Co-authored-by: Facundo <[email protected]> Co-authored-by: marbar3778 <[email protected]> Co-authored-by: Julien Robert <[email protected]>
This is a partial backport of cosmos#18047. Txs were not migrated. EndBlocker behaviour was not changed since v47 x/feegrant::EndBlocker cannot produce an error during operation.
Description
This PR adds a limit to the amount of expired grants that the EndBlocker remove and adds a tx that allows users of a chain to prune more.
My understanding is that EndBlocker is supposed to do "automatic" work, but we need to limit, and here we do that + give the option to users to help in pruning.
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
make lint
andmake test
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change