-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[bugfix][protocol] fix settled funding event emission #1051
Conversation
Warning Rate Limit Exceeded@lucas-dydx has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 24 minutes and 15 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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. WalkthroughThe recent update involves a modification in the naming convention of an attribute key within the Changes
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? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
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.
non-blocking nit:
How hard is it to update a test for this?
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.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files selected for processing (1)
- protocol/x/subaccounts/types/events.go (1 hunks)
Additional comments: 1
protocol/x/subaccounts/types/events.go (1)
- 30-30: The change from
AttributeKeySubaccount
toAttributeKeySubaccountNumber
in theNewCreateSettledFundingEvent
function correctly addresses the bug affecting event indexers. Ensure all downstream systems expectingAttributeKeySubaccount
are updated to handleAttributeKeySubaccountNumber
.
* [bugfix][protocol] fix settled funding event emission * add TODO (cherry picked from commit ab6a65c)
Changelist
Update the event key for subaccount number. Bug was found since downstream event indexers broke.
Note this shouldn't be consensus-breaking since this only changes event emissions.
Test Plan
N/A since trying to get this in next release.
Author/Reviewer Checklist
state-breaking
label.indexer-postgres-breaking
label.PrepareProposal
orProcessProposal
, manually add the labelproposal-breaking
.feature:[feature-name]
.backport/[branch-name]
.refactor
,chore
,bug
.