Skip to content
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

fix(x/staking): use staking bonddenom in check #22646

Merged
merged 3 commits into from
Nov 26, 2024
Merged

Conversation

julienrbrt
Copy link
Member

@julienrbrt julienrbrt commented Nov 25, 2024

Description

Closes: #22645


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...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

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.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • New Features
    • Enhanced validation logic for key rotation fees, ensuring the bond denomination is checked alongside the fee.
  • Bug Fixes
    • Updated error messages for improved clarity regarding validation parameters.

Copy link
Contributor

coderabbitai bot commented Nov 25, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The changes in this pull request involve modifications to the Validate method of the Params struct and the validateKeyRotationFee function in x/staking/types/params.go. The Validate method now includes an additional parameter, BondDenom, which is passed to the validateKeyRotationFee function. This function has been refactored to validate the bondDenom string, ensuring it is not blank and adjusting error messages accordingly. The validation logic for the key rotation fee has been enhanced to incorporate checks for the bondDenom.

Changes

File Change Summary
x/staking/types/params.go Updated Validate method to pass BondDenom to validateKeyRotationFee. Refactored the function to validate bondDenom and adjust error messages.

Possibly related PRs

Suggested reviewers

  • ziscky
  • facundomedica
  • testinginprod
  • akhilkumarpilli

📜 Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4a638b1 and 379f343.

📒 Files selected for processing (1)
  • x/staking/types/params.go (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • x/staking/types/params.go

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@julienrbrt your pull request is missing a changelog!

@julienrbrt julienrbrt added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Nov 25, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 2d04a1a and 4a638b1.

📒 Files selected for processing (1)
  • x/staking/types/params.go (2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
x/staking/types/params.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

🔇 Additional comments (1)
x/staking/types/params.go (1)

113-113: LGTM: Correctly passing BondDenom to validation function

The change properly forwards the bond denomination to the validation function, ensuring consistent denomination checking.

Comment on lines 218 to 228
func validateKeyRotationFee(bondDenom string, coin sdk.Coin) error {
if strings.TrimSpace(bondDenom) == "" {
return errors.New("bond denom cannot be blank")
}

if v.IsNil() {
return fmt.Errorf("cons pubkey rotation fee cannot be nil: %s", v)
if coin.IsNil() {
return fmt.Errorf("cons pubkey rotation fee cannot be nil: %s", coin)
}
if v.IsLTE(sdk.NewInt64Coin(sdk.DefaultBondDenom, 0)) {
return fmt.Errorf("cons pubkey rotation fee cannot be negative or zero: %s", v)

if coin.IsLTE(sdk.NewInt64Coin(bondDenom, 0)) {
return fmt.Errorf("cons pubkey rotation fee cannot be negative or zero: %s", coin)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Several improvements needed in validateKeyRotationFee

  1. The error messages inconsistently refer to "cons pubkey rotation fee" while the variable is named "KeyRotationFee"
  2. Missing validation to ensure the coin's denomination matches the bondDenom
  3. Consider reusing the existing validateBondDenom function instead of duplicating the blank check logic

Here's the suggested implementation:

 func validateKeyRotationFee(bondDenom string, coin sdk.Coin) error {
-    if strings.TrimSpace(bondDenom) == "" {
-        return errors.New("bond denom cannot be blank")
-    }
+    if err := validateBondDenom(bondDenom); err != nil {
+        return err
+    }

     if coin.IsNil() {
-        return fmt.Errorf("cons pubkey rotation fee cannot be nil: %s", coin)
+        return fmt.Errorf("key rotation fee cannot be nil: %s", coin)
     }

+    if coin.Denom != bondDenom {
+        return fmt.Errorf("key rotation fee denom %s must match bond denom %s", 
+            coin.Denom, bondDenom)
+    }

     if coin.IsLTE(sdk.NewInt64Coin(bondDenom, 0)) {
-        return fmt.Errorf("cons pubkey rotation fee cannot be negative or zero: %s", coin)
+        return fmt.Errorf("key rotation fee cannot be negative or zero: %s", coin)
     }

     return nil
}
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
func validateKeyRotationFee(bondDenom string, coin sdk.Coin) error {
if strings.TrimSpace(bondDenom) == "" {
return errors.New("bond denom cannot be blank")
}
if v.IsNil() {
return fmt.Errorf("cons pubkey rotation fee cannot be nil: %s", v)
if coin.IsNil() {
return fmt.Errorf("cons pubkey rotation fee cannot be nil: %s", coin)
}
if v.IsLTE(sdk.NewInt64Coin(sdk.DefaultBondDenom, 0)) {
return fmt.Errorf("cons pubkey rotation fee cannot be negative or zero: %s", v)
if coin.IsLTE(sdk.NewInt64Coin(bondDenom, 0)) {
return fmt.Errorf("cons pubkey rotation fee cannot be negative or zero: %s", coin)
func validateKeyRotationFee(bondDenom string, coin sdk.Coin) error {
if err := validateBondDenom(bondDenom); err != nil {
return err
}
if coin.IsNil() {
return fmt.Errorf("key rotation fee cannot be nil: %s", coin)
}
if coin.Denom != bondDenom {
return fmt.Errorf("key rotation fee denom %s must match bond denom %s",
coin.Denom, bondDenom)
}
if coin.IsLTE(sdk.NewInt64Coin(bondDenom, 0)) {
return fmt.Errorf("key rotation fee cannot be negative or zero: %s", coin)
}
return nil
}

💡 Codebase verification

Additional test coverage needed for key rotation fee validation

The current test coverage in params_test.go is insufficient for the new validation logic. While there is a basic test for zero coins, it's missing tests for:

  • Blank bond denomination validation
  • Nil coin validation
  • Negative coin validation
  • Mismatched denomination validation

Please add test cases to cover these scenarios in the TestValidateParams function:

// Test cases to add:
params.BondDenom = ""  // blank denomination
params.KeyRotationFee = nil  // nil coin
params.KeyRotationFee = sdk.NewInt64Coin("stake", -1)  // negative amount
params.KeyRotationFee = sdk.NewInt64Coin("different", 100)  // mismatched denom
🔗 Analysis chain

Verify test coverage for the new validation logic

Please ensure that unit tests cover:

  1. Validation with mismatched denominations
  2. Validation with blank bond denomination
  3. Validation with nil and non-positive coins
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for relevant test cases in the codebase
rg -l "TestValidateKeyRotationFee|TestParams_Validate" "x/staking/types"

Length of output: 72


Script:

#!/bin/bash
# Let's try a broader search for test files in the staking types directory
fd ".*_test.go" "x/staking/types"

# Then let's look for any test cases related to params validation
rg -A 5 "func.*Test.*Param" "x/staking/types"

# Also search for any test cases containing "KeyRotation"
rg -A 5 "KeyRotation.*Test" "x/staking/types"

Length of output: 1038


Script:

#!/bin/bash
# Let's examine the content of params_test.go to see the existing test coverage
cat "x/staking/types/params_test.go"

Length of output: 1016

Copy link
Contributor

@akhilkumarpilli akhilkumarpilli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, small nit.

x/staking/types/params.go Outdated Show resolved Hide resolved
Copy link
Contributor

@JulianToledano JulianToledano left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@julienrbrt julienrbrt enabled auto-merge November 26, 2024 08:09
@julienrbrt julienrbrt added this pull request to the merge queue Nov 26, 2024
Merged via the queue into main with commit a60dfda Nov 26, 2024
74 of 75 checks passed
@julienrbrt julienrbrt deleted the julien/bondenom branch November 26, 2024 08:28
mergify bot pushed a commit that referenced this pull request Nov 26, 2024
julienrbrt added a commit that referenced this pull request Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release C:x/staking
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: x/staking param validation assumes denom name of 'stake'
6 participants