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/auth/tx): avoid panic from intoAnyV2 when v1.PublicKey is optional #23148

Merged
merged 5 commits into from
Jan 3, 2025

Conversation

mmsqe
Copy link
Contributor

@mmsqe mmsqe commented Jan 2, 2025

Description

Closes: #XXXX


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

  • Bug Fixes
    • Resolved a potential panic in the x/auth/tx module when handling optional PublicKey values.
    • Improved error handling for the intoV2SignerInfo function to prevent nil dereference issues.
  • Tests
    • Added unit tests for the intoV2SignerInfo function to ensure expected behavior with various inputs.

Copy link
Contributor

coderabbitai bot commented Jan 2, 2025

📝 Walkthrough

Walkthrough

This pull request introduces a bug fix for the Cosmos SDK's x/auth/tx module by adding a changelog entry that addresses a potential panic issue related to the intoAnyV2 function when the v1.PublicKey is optional. Additionally, modifications to the intoV2SignerInfo function in builder.go enhance its robustness by incorporating a nil check for the PublicKey field. A new test case has also been added to ensure the correct behavior of the updated function.

Changes

File Change Summary
CHANGELOG.md Added bug fix entry for x/auth/tx module addressing potential panic with optional PublicKey
x/auth/tx/builder.go Modified intoV2SignerInfo function to include nil check for PublicKey before assignment
x/auth/tx/builder_test.go Added new test function TestIntoV2SignerInfo to verify behavior of intoV2SignerInfo function

Possibly related PRs

  • chore: add crisis changelog #22280: The changes in the main PR regarding the CHANGELOG.md are related to this PR, which also involves updates to the changelog for the Cosmos SDK, ensuring clarity and organization of documented changes.
  • fix(x/tx): add feePayer as signer #22311: This PR updates the changelog to include a fix for adding feePayer as a signer, which is relevant to the main PR's focus on bug fixes in the x/auth/tx module.
  • test: x/accounts systemtests #22320: The system tests introduced in this PR for the x/accounts module may relate to the overall changes in the x/auth/tx module, as both are part of the broader account management functionalities in the Cosmos SDK.
  • docs: fix multiple typos #23143: This PR focuses on fixing multiple typos in the documentation, which may include references to the x/auth/tx module, aligning with the main PR's updates to the changelog and documentation clarity.
  • docs: fix typos #23152: Similar to the previous PR, this one addresses typos in the documentation related to the x/accounts module, which is relevant to the changes in the main PR that involve updates to the CHANGELOG.md and documentation.

Suggested Labels

Type: CI

Suggested Reviewers

  • sontrinh16
  • tac0turtle
  • julienrbrt
  • testinginprod

📜 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 ae4e0de and cc20a3d.

📒 Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • CHANGELOG.md

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.

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 (3)
CHANGELOG.md (3)

Line range hint 1-1: Add missing title to changelog file

The changelog file should start with a clear title like "# Changelog" to follow standard markdown practices.

+ # Changelog

53-53: Fix inconsistent version link formatting

The version link format is inconsistent with other version links in the document. It should follow the same pattern as other version links.

- ## v0.47.15 - 2024-12-16
+ ## [v0.47.15](https://github.com/cosmos/cosmos-sdk/releases/tag/v0.47.15) - 2024-12-16

Also applies to: 54-54


Line range hint 2892-2892: Remove redundant empty code block

The empty code block at the end of the file serves no purpose and should be removed.

- ```
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d39d0bc and b7471fb.

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

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

CHANGELOG.md (1)

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

🔇 Additional comments (2)
x/auth/tx/builder.go (1)

296-300: Ensure robust handling of nil PublicKey

These lines correctly handle the scenario when v1.PublicKey is nil by checking before calling intoAnyV2. This aligns with the PR’s goal of preventing possible panics. Please also confirm that test coverage includes cases where PublicKey is intentionally left unset to validate this logic works as expected.

CHANGELOG.md (1)

Line range hint 1-2892: LGTM on overall changelog structure and content

The changelog follows good practices by:

  • Organizing changes by version with clear release dates
  • Categorizing changes into features, improvements, bug fixes etc.
  • Including PR references
  • Providing detailed descriptions of breaking changes

Copy link
Contributor

@testinginprod testinginprod left a comment

Choose a reason for hiding this comment

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

i'd add a test case to cover this

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 (2)
x/auth/tx/builder_test.go (2)

6-6: Consider renaming the import alias for clarity.
Currently, the alias any might be confused with Go’s any type. Consider using a more descriptive alias, e.g., protoAny.

-import (
-	any "github.com/cosmos/gogoproto/types/any"
-	"github.com/stretchr/testify/require"
-	...
-)
+import (
+	protoAny "github.com/cosmos/gogoproto/types/any"
+	"github.com/stretchr/testify/require"
+	...
+)

12-15: Expand test assertions for better coverage.
Currently, you’re only checking that the result is non-nil. Consider asserting other properties (e.g., length, content) to ensure intoV2SignerInfo behaves correctly under different permutations (like providing actual data vs. empty arrays).

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b7471fb and ae4e0de.

📒 Files selected for processing (1)
  • x/auth/tx/builder_test.go (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
x/auth/tx/builder_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"

@tac0turtle tac0turtle added this pull request to the merge queue Jan 3, 2025
Merged via the queue into cosmos:main with commit 07d5168 Jan 3, 2025
68 of 70 checks passed
@julienrbrt
Copy link
Member

@Mergifyio backport release/v0.52.x

Copy link
Contributor

mergify bot commented Jan 6, 2025

backport release/v0.52.x

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Jan 6, 2025
…nal (#23148)

(cherry picked from commit 07d5168)

# Conflicts:
#	CHANGELOG.md
julienrbrt added a commit that referenced this pull request Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants