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): fix validator metadata update #23461

Merged
merged 4 commits into from
Jan 20, 2025

Conversation

ziscky
Copy link
Contributor

@ziscky ziscky commented Jan 20, 2025

Description

Closes: #23413


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 validator description with metadata support.
    • Added ability to update validator profile information, including profile picture and social media handles.
    • Introduced parsing of metadata-profile-pic-uri in the create-validator JSON and a new CLI flag for edit-validator.
  • Bug Fixes

    • Fixed the UpdateDescription function to ensure it correctly updates the Metadata field.
  • Tests

    • Expanded test coverage for description update functionality with metadata handling.

These changes improve the flexibility of validator descriptions by allowing more comprehensive profile information while maintaining existing core functionality.

@ziscky ziscky requested review from JulianToledano and a team as code owners January 20, 2025 08:49
Copy link
Contributor

coderabbitai bot commented Jan 20, 2025

📝 Walkthrough

Walkthrough

The pull request addresses a bug in the UpdateDescription method of the Description struct within the staking module. The change modifies how metadata is handled during validator description updates, specifically fixing an issue where metadata was not being correctly updated due to passing the wrong metadata parameter to the NewDescription function. Additionally, the test cases have been updated to reflect these changes, ensuring proper functionality.

Changes

File Change Summary
x/staking/types/validator.go Modified UpdateDescription method to correctly pass d2.Metadata instead of d.Metadata
x/staking/types/validator_test.go Added Metadata field to Description struct and updated TestUpdateDescription to include metadata handling
x/staking/CHANGELOG.md Updated changelog to reflect new features, improvements, and bug fixes related to metadata handling

Assessment against linked issues

Objective Addressed Explanation
Fix metadata update bug [#23413]
Ensure correct metadata handling in UpdateDescription

Suggested Labels

C:Store

Suggested Reviewers

  • ziscky
  • JulianToledano
  • kocubinski
  • testinginprod
  • akhilkumarpilli

📜 Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 99d613b and 89f2103.

📒 Files selected for processing (1)
  • x/staking/CHANGELOG.md (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • x/staking/CHANGELOG.md
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Summary

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

This comment has been minimized.

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: 0

🧹 Nitpick comments (1)
x/staking/types/validator_test.go (1)

35-38: LGTM! Consider adding more test cases.

The test cases effectively cover the basic metadata update scenarios. However, consider adding tests for:

  • Invalid profile picture URI
  • Invalid social handle URIs
  • Nil metadata updates

Also applies to: 46-49, 57-57

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f9bb180 and e85dcfb.

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

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

x/staking/types/validator_test.go (2)

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


Pattern **/*_test.go: "Assess the unit test code assessing sufficient code coverage for the changes associated in the pull request"

⏰ Context from checks skipped due to timeout of 90000ms (6)
  • GitHub Check: tests (00)
  • GitHub Check: test-simapp-v2
  • GitHub Check: test-system-v2
  • GitHub Check: build (amd64)
  • GitHub Check: Analyze
  • GitHub Check: Summary
🔇 Additional comments (1)
x/staking/types/validator.go (1)

242-242: LGTM! The metadata update fix is correct.

The change properly handles metadata updates by passing d2.Metadata instead of d.Metadata, consistent with how other Description fields are updated.

Let's verify that this is the only instance where metadata needs to be updated:

✅ Verification successful

✓ Metadata update change is correct and complete

The verification confirms this is the only instance of NewDescription usage, and the metadata update follows the established pattern with proper validation flow. The change from d.Metadata to d2.Metadata is consistent with the codebase's metadata handling logic, including the DoNotModify check implemented earlier in the function.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for other potential metadata update locations
ast-grep --pattern 'NewDescription($$$, metadata)'

Length of output: 52


Script:

#!/bin/bash
# Search for all NewDescription calls
ast-grep --pattern 'NewDescription($$$)'

# Also search for metadata references in the context
rg "Metadata" -A 2 -B 2 x/staking/types/validator.go

Length of output: 1701

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: 0

🧹 Nitpick comments (1)
x/staking/CHANGELOG.md (1)

59-59: Enhance the changelog message with more details.

While the format is correct, consider making the changelog message more descriptive by explaining the previous behavior and the impact. For example:

-* [#23461](https://github.com/cosmos/cosmos-sdk/pull/23461) Fix `UpdateDescription` to correctly update the `Metadata` field.
+* [#23461](https://github.com/cosmos/cosmos-sdk/pull/23461) Fix `UpdateDescription` to correctly update the `Metadata` field by passing the new description's metadata instead of the existing metadata, ensuring validator metadata updates are properly applied.
📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e85dcfb and 99d613b.

📒 Files selected for processing (1)
  • x/staking/CHANGELOG.md (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
x/staking/CHANGELOG.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness"

⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: test-system-v2
  • GitHub Check: Analyze
  • GitHub Check: Summary

@@ -56,6 +56,7 @@ Ref: https://keepachangelog.com/en/1.0.0/

* [#20688](https://github.com/cosmos/cosmos-sdk/pull/20688) Avoid overslashing unbonding delegations after a redelegation.
* [#19226](https://github.com/cosmos/cosmos-sdk/pull/19226) Ensure `GetLastValidators` in `x/staking` does not return an error when `MaxValidators` exceeds total number of bonded validators.
* [#23461](https://github.com/cosmos/cosmos-sdk/pull/23461) Fix `UpdateDescription` to correctly update the `Metadata` field.
Copy link
Member

Choose a reason for hiding this comment

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

no changelog needed, this feature is on main only.

Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

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

ACK, but no need to add a changelog

@aljo242 aljo242 enabled auto-merge January 20, 2025 16:37
@aljo242 aljo242 added this pull request to the merge queue Jan 20, 2025
Merged via the queue into main with commit 84a32cc Jan 20, 2025
72 of 73 checks passed
@aljo242 aljo242 deleted the ziscky/23413-validator-metadata-update-fix branch January 20, 2025 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug]: Cannot update Validator Description Metadata
5 participants