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

chore(x/feegrant): use cosmossdk.io/core/codec instead of github.com/cosmos/cosmos-sdk/codec #23297

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

caseylove
Copy link
Contributor

@caseylove caseylove commented Jan 10, 2025

Description

Partially addresses: #23253

Summary by CodeRabbit

  • Refactor

    • Updated codec dependency from cosmos-sdk/codec to cosmossdk.io/core/codec
    • Improved error handling in DefaultGenesis method and NewDecodeStore function
    • Replaced MustMarshalJSON and MustUnmarshal with methods that allow explicit error management
  • Chores

    • Updated import statements to use new codec package

@caseylove caseylove requested review from alpe and a team as code owners January 10, 2025 03:53
Copy link
Contributor

coderabbitai bot commented Jan 10, 2025

Warning

Rate limit exceeded

@julienrbrt has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 22 minutes and 34 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 for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 517839b and c0ac2f9.

📒 Files selected for processing (3)
  • x/feegrant/migrations/v2/store.go (1 hunks)
  • x/feegrant/module/module.go (2 hunks)
  • x/feegrant/simulation/decoder.go (2 hunks)

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.

@caseylove caseylove changed the title chore(x/feegrant-codec): use cosmossdk.io/core/codec instead of github.com/cosmos/cosmos-sdk/codec chore(x/feegrant): use cosmossdk.io/core/codec instead of github.com/cosmos/cosmos-sdk/codec Jan 10, 2025
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: 4

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 517839b and a133656.

📒 Files selected for processing (2)
  • x/feegrant/module/module.go (2 hunks)
  • x/feegrant/simulation/decoder.go (2 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
x/feegrant/module/module.go (1)

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

x/feegrant/simulation/decoder.go (1)

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

🪛 golangci-lint (1.62.2)
x/feegrant/module/module.go

19-19: File is not gci-ed with --skip-generated -s standard -s default -s prefix(cosmossdk.io) -s prefix(github.com/cosmos/cosmos-sdk) --custom-order

(gci)

🪛 GitHub Actions: Lint
x/feegrant/module/module.go

[error] 12-12: File is not gci-ed with --skip-generated -s standard -s default -s prefix(cosmossdk.io) -s prefix(github.com/cosmos/cosmos-sdk) --custom-order


[error] 19-19: File is not gci-ed with --skip-generated -s standard -s default -s prefix(cosmossdk.io) -s prefix(github.com/cosmos/cosmos-sdk) --custom-order

x/feegrant/simulation/decoder.go

[error] 8-8: File is not gci-ed with --skip-generated -s standard -s default -s prefix(cosmossdk.io) -s prefix(github.com/cosmos/cosmos-sdk) --custom-order

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

@@ -4,9 +4,8 @@ import (
"bytes"
"fmt"

"cosmossdk.io/core/codec"
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix import ordering using gci.

The imports need to be reordered according to the project's guidelines using gci with the following configuration:

gci --skip-generated -s standard -s default -s prefix(cosmossdk.io) -s prefix(github.com/cosmos/cosmos-sdk)

Comment on lines +19 to +24
if err := cdc.Unmarshal(kvA.Value, &grantA); err != nil {
panic(err)
}
if err := cdc.Unmarshal(kvB.Value, &grantB); err != nil {
panic(err)
}
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

Consider using error propagation instead of panic.

While the error handling is more explicit now, using panic in production code is generally discouraged. Consider propagating the error up the call stack instead.

-func NewDecodeStore(cdc codec.Codec) func(kvA, kvB kv.Pair) string {
+func NewDecodeStore(cdc codec.Codec) func(kvA, kvB kv.Pair) (string, error) {
-	return func(kvA, kvB kv.Pair) string {
+	return func(kvA, kvB kv.Pair) (string, error) {
 		switch {
 		case bytes.Equal(kvA.Key[:1], feegrant.FeeAllowanceKeyPrefix):
 			var grantA, grantB feegrant.Grant
 			if err := cdc.Unmarshal(kvA.Value, &grantA); err != nil {
-				panic(err)
+				return "", fmt.Errorf("failed to unmarshal grant A: %w", err)
 			}
 			if err := cdc.Unmarshal(kvB.Value, &grantB); err != nil {
-				panic(err)
+				return "", fmt.Errorf("failed to unmarshal grant B: %w", err)
 			}
-			return fmt.Sprintf("%v\n%v", grantA, grantB)
+			return fmt.Sprintf("%v\n%v", grantA, grantB), nil
 		default:
-			panic(fmt.Sprintf("invalid feegrant key %X", kvA.Key))
+			return "", fmt.Errorf("invalid feegrant key %X", kvA.Key)
 		}
 	}
 }
📝 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
if err := cdc.Unmarshal(kvA.Value, &grantA); err != nil {
panic(err)
}
if err := cdc.Unmarshal(kvB.Value, &grantB); err != nil {
panic(err)
}
func NewDecodeStore(cdc codec.Codec) func(kvA, kvB kv.Pair) (string, error) {
return func(kvA, kvB kv.Pair) (string, error) {
switch {
case bytes.Equal(kvA.Key[:1], feegrant.FeeAllowanceKeyPrefix):
var grantA, grantB feegrant.Grant
if err := cdc.Unmarshal(kvA.Value, &grantA); err != nil {
return "", fmt.Errorf("failed to unmarshal grant A: %w", err)
}
if err := cdc.Unmarshal(kvB.Value, &grantB); err != nil {
return "", fmt.Errorf("failed to unmarshal grant B: %w", err)
}
return fmt.Sprintf("%v\n%v", grantA, grantB), nil
default:
return "", fmt.Errorf("invalid feegrant key %X", kvA.Key)
}
}
}

@@ -16,8 +16,8 @@ import (
"cosmossdk.io/x/feegrant/client/cli"
"cosmossdk.io/x/feegrant/keeper"

"cosmossdk.io/core/codec"
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix import ordering using gci.

The imports need to be reordered according to the project's guidelines using gci with the following configuration:

gci --skip-generated -s standard -s default -s prefix(cosmossdk.io) -s prefix(github.com/cosmos/cosmos-sdk)
🧰 Tools
🪛 golangci-lint (1.62.2)

19-19: File is not gci-ed with --skip-generated -s standard -s default -s prefix(cosmossdk.io) -s prefix(github.com/cosmos/cosmos-sdk) --custom-order

(gci)

🪛 GitHub Actions: Lint

[error] 19-19: File is not gci-ed with --skip-generated -s standard -s default -s prefix(cosmossdk.io) -s prefix(github.com/cosmos/cosmos-sdk) --custom-order

Comment on lines +106 to +110
data, err := am.cdc.MarshalJSON(feegrant.DefaultGenesisState())
if err != nil {
panic(err)
}
return data
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

Consider using error propagation instead of panic.

While the error handling is more explicit now, using panic in production code is generally discouraged. Consider propagating the error up the call stack by updating the interface to return an error.

-func (am AppModule) DefaultGenesis() json.RawMessage {
+func (am AppModule) DefaultGenesis() (json.RawMessage, error) {
 	data, err := am.cdc.MarshalJSON(feegrant.DefaultGenesisState())
 	if err != nil {
-		panic(err)
+		return nil, fmt.Errorf("failed to marshal default genesis state: %w", err)
 	}
-	return data
+	return data, nil
}

Committable suggestion skipped: line range outside the PR's diff.

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

@julienrbrt julienrbrt added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Jan 10, 2025
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:Simulations C:x/feegrant
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants