Closed mattverse closed 5 months ago
Because this isn't state compatible, lets target the osmo/v0.47.5 branch. That will behave like our "main" branch
@czarcas7ic I think https://github.com/osmosis-labs/cosmos-sdk/commit/54cc86a9682730648ab8ec6b2ee597f1ff9b1609 this PR also might have been state breaking should we revert it and also have it targeted toward osmo/v0.47.5 branch?
[!WARNING]
Rate Limit Exceeded
@czarcas7ic has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 3 minutes and 11 seconds before requesting another review.
How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.How do rate limits work?
CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://coderabbit.ai/docs/faq) for further information.Commits
Files that changed from the base of the PR and between 910b67d733caccbe111d2f50cbb15ae8447e18b1 and 155e7ad035c03486658eb38cdf2bd9eab65560e8.
The recent updates involve modifying the DequeueAndDeleteExpiredGrants
function in the Keeper
structure to accept an additional limit
parameter. This adjustment allows for controlling the number of iterations and consequently, the records pruned during each execution to avoid excessive processing time. Accompanying tests ensure the functionality behaves as expected with various limit
values. Additionally, the BeginBlocker
function now incorporates this change by specifying a limit when calling DequeueAndDeleteExpiredGrants
, aiming to enhance performance and reliability in handling expired grants.
Files | Change Summary |
---|---|
.../keeper/keeper.go .../keeper/keeper_test.go |
Added limit int parameter to DequeueAndDeleteExpiredGrants in Keeper ; introduced tests for different limit values. |
.../module/abci.go |
Modified BeginBlocker to call DequeueAndDeleteExpiredGrants with a 200 limit. |
🐰✨
In the realm of code, where the bits align,
A rabbit hopped in, with a change so fine.
"Let's limit our loops," it said with a grin,
"To keep our system sprightly, and let efficiency win."
So with a tweak and a test, the job was done,
Now the code runs smoother, under the virtual sun.
🌟🐇
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Description
Backport of PR 18737 and PR 19315 from upstream
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
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 changeSummary by CodeRabbit