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

feat(serverv2/cometbft) Read config from commands & handle FlagNode #20621

Merged
merged 5 commits into from
Jun 12, 2024

Conversation

hieuvubk
Copy link
Contributor

@hieuvubk hieuvubk commented Jun 11, 2024

Description

Closes: #20610

  • Read comet config from commands
  • rpcClient checks if flags.FlagNode existed in cmd then handle
  • Tested in local

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

  • Refactor
    • Improved command handling by adjusting various functions to pass command parameters, enhancing flexibility and configurability.

@hieuvubk hieuvubk requested a review from a team as a code owner June 11, 2024 10:07
Copy link
Contributor

coderabbitai bot commented Jun 11, 2024

Warning

Rate limit exceeded

@hieuvubk has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 46 minutes and 17 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

Files that changed from the base of the PR and between 382207c and e999f74.

Walkthrough

The changes in the server/v2/cometbft/commands.go file involve updating the rpcClient method in the CometBFTServer struct to accept a cmd *cobra.Command parameter. This adjustment ensures that configurations are read directly from the command instead of relying on potentially uninitialized nested structures within the server. Various command functions within the CometBFTServer struct have been updated to pass the cmd parameter to the rpcClient method and to use client.GetConfigFromCmd(cmd).

Changes

File Path Change Summary
server/v2/cometbft/commands.go Modified rpcClient method to accept cmd *cobra.Command parameter. Updated command functions to pass cmd and use client.GetConfigFromCmd(cmd).

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CobraCommand
    participant CometBFTServer
    participant rpcClient
    participant Config

    User ->> CobraCommand: Executes Command
    CobraCommand ->> CometBFTServer: Calls Command Function
    CometBFTServer ->> rpcClient: Passes cmd to rpcClient(cmd)
    rpcClient ->> Config: Fetches Config using cmd
    Config ->> rpcClient: Returns Config
    rpcClient ->> CometBFTServer: Returns rpcClient instance
    CometBFTServer ->> User: Executes Command Logic
Loading

Assessment against linked issues

Objective Addressed Explanation
Read CmtConfig from cmd instead of getting it from struct (#20610)
Ensure commands do not rely on nested structure inside CometBFTServer (#20610)

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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

@hieuvubk your pull request is missing a changelog!

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

Outside diff range and nitpick comments (1)
server/v2/cometbft/commands.go (1)

Line range hint 404-417: Ensure error handling for configuration and state initialization in BootstrapStateCmd.

The BootstrapStateCmd function lacks comprehensive error handling for configuration retrieval and state initialization, which could lead to failures during runtime:

+ if cfg == nil {
+     return fmt.Errorf("failed to retrieve configuration")
+ }
+ if height == 0 && err != nil {
+     return fmt.Errorf("failed to retrieve latest version: %w", err)
+ }
Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 62aa118 and 382207c.

Files selected for processing (1)
  • server/v2/cometbft/commands.go (10 hunks)
Additional context used
Path-based instructions (1)
server/v2/cometbft/commands.go (1)

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

Comment on lines 32 to 47
func (s *CometBFTServer[T]) rpcClient(cmd *cobra.Command) (rpc.CometRPC, error) {
if s.config.Standalone {
client, err := rpchttp.New(s.config.CmtConfig.RPC.ListenAddress)
client, err := rpchttp.New(client.GetConfigFromCmd(cmd).RPC.ListenAddress)
if err != nil {
return nil, err
}
return client, nil
}

if s.Node == nil || cmd.Flags().Changed(flags.FlagNode) {
rpcURI, _ := cmd.Flags().GetString(flags.FlagNode)
if rpcURI != "" {
return rpchttp.New(rpcURI)
}
}

Copy link
Contributor

Choose a reason for hiding this comment

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

Consider handling the error when fetching the FlagNode string.

The current implementation assumes successful retrieval of the FlagNode string without checking for errors. This could lead to unexpected behavior if the flag is not set or there is an issue with the command flags. Consider adding error handling:

- rpcURI, _ := cmd.Flags().GetString(flags.FlagNode)
+ rpcURI, err := cmd.Flags().GetString(flags.FlagNode)
+ if err != nil {
+     return nil, fmt.Errorf("failed to get FlagNode: %w", err)
+ }
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 (s *CometBFTServer[T]) rpcClient(cmd *cobra.Command) (rpc.CometRPC, error) {
if s.config.Standalone {
client, err := rpchttp.New(s.config.CmtConfig.RPC.ListenAddress)
client, err := rpchttp.New(client.GetConfigFromCmd(cmd).RPC.ListenAddress)
if err != nil {
return nil, err
}
return client, nil
}
if s.Node == nil || cmd.Flags().Changed(flags.FlagNode) {
rpcURI, _ := cmd.Flags().GetString(flags.FlagNode)
if rpcURI != "" {
return rpchttp.New(rpcURI)
}
}
func (s *CometBFTServer[T]) rpcClient(cmd *cobra.Command) (rpc.CometRPC, error) {
if s.config.Standalone {
client, err := rpchttp.New(client.GetConfigFromCmd(cmd).RPC.ListenAddress)
if err != nil {
return nil, err
}
return client, nil
}
if s.Node == nil || cmd.Flags().Changed(flags.FlagNode) {
rpcURI, err := cmd.Flags().GetString(flags.FlagNode)
if err != nil {
return nil, fmt.Errorf("failed to get FlagNode: %w", err)
}
if rpcURI != "" {
return rpchttp.New(rpcURI)
}
}

Comment on lines +91 to +92
cmtConfig := client.GetConfigFromCmd(cmd)
nodeKey, err := p2p.LoadNodeKey(cmtConfig.NodeKeyFile())
Copy link
Contributor

Choose a reason for hiding this comment

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

Validate the existence of NodeKeyFile before attempting to load it.

The ShowNodeIDCmd function attempts to load a node key file without prior validation of its existence or accessibility, which could lead to runtime errors if the file is missing or inaccessible:

+ if _, err := os.Stat(cmtConfig.NodeKeyFile()); os.IsNotExist(err) {
+     return fmt.Errorf("node key file does not exist: %s", cmtConfig.NodeKeyFile())
+ }

Committable suggestion was skipped due to low confidence.

@@ -241,7 +250,7 @@
RunE: func(cmd *cobra.Command, args []string) error {
typ, _ := cmd.Flags().GetString(auth.FlagType)

rpcclient, err := s.rpcClient()
rpcclient, err := s.rpcClient(cmd)
Copy link
Contributor

Choose a reason for hiding this comment

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

Improve error messages for user clarity in QueryBlockCmd.

The error messages in QueryBlockCmd are generic and do not provide enough context to the user about what went wrong. Enhancing these messages can improve user experience:

- return fmt.Errorf("argument should be a block height")
+ return fmt.Errorf("invalid argument: expected a block height, got '%s'", args[0])
- return fmt.Errorf("no block found with height %s", args[0])
+ return fmt.Errorf("no block found with the specified height: %s", args[0])
- return fmt.Errorf("no block found with hash %s", args[0])
+ return fmt.Errorf("no block found with the specified hash: %s", args[0])

Also applies to: 253-253

Committable suggestion was skipped due to low confidence.

@@ -188,7 +197,7 @@
version.AppName,
),
RunE: func(cmd *cobra.Command, args []string) error {
rpcclient, err := s.rpcClient()
rpcclient, err := s.rpcClient(cmd)
Copy link
Contributor

Choose a reason for hiding this comment

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

Refactor repeated error handling in QueryBlocksCmd for clarity and maintenance.

The error handling in QueryBlocksCmd is repetitive and could be streamlined for better readability and maintenance:

- if err != nil {
-     return err
- }
+ if err != nil {
+     return fmt.Errorf("failed to query blocks: %w", err)
+ }

Also applies to: 200-200

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
rpcclient, err := s.rpcClient(cmd)
rpcclient, err := s.rpcClient(cmd)
if err != nil {
return fmt.Errorf("failed to query blocks: %w", err)
}

@@ -46,7 +54,7 @@
Use: "status",
Short: "Query remote node for status",
RunE: func(cmd *cobra.Command, _ []string) error {
rpcclient, err := s.rpcClient()
rpcclient, err := s.rpcClient(cmd)
Copy link
Contributor

Choose a reason for hiding this comment

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

Ensure proper error handling and user feedback for command execution.

The StatusCommand function lacks detailed error messages which could help in diagnosing issues more effectively. Consider enhancing the error handling:

- return err
+ return fmt.Errorf("failed to get RPC client: %w", err)
- return err
+ return fmt.Errorf("failed to get status from RPC client: %w", err)
- return err
+ return fmt.Errorf("failed to marshal status output: %w", err)

Also applies to: 57-57

Committable suggestion was skipped due to low confidence.

@@ -332,7 +341,7 @@

// TODO: we should be able to do this without using client context

node, err := s.rpcClient()
node, err := s.rpcClient(cmd)
Copy link
Contributor

Choose a reason for hiding this comment

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

Add error handling for potential nil pointer in QueryBlockResultsCmd.

The function QueryBlockResultsCmd does not handle the scenario where node could be nil after an error, which might lead to a runtime panic:

+ if node == nil {
+     return fmt.Errorf("RPC client is unavailable")
+ }

Also applies to: 344-344

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
node, err := s.rpcClient(cmd)
node, err := s.rpcClient(cmd)
if node == nil {
return fmt.Errorf("RPC client is unavailable")
}

@@ -97,7 +106,7 @@
Use: "show-validator",
Short: "Show this node's CometBFT validator info",
RunE: func(cmd *cobra.Command, args []string) error {
cfg := s.config.CmtConfig
cfg := client.GetConfigFromCmd(cmd)
Copy link
Contributor

Choose a reason for hiding this comment

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

Handle potential nil pointer dereference in ShowValidatorCmd.

The function ShowValidatorCmd does not check if privValidator is nil after loading, which could lead to a nil pointer dereference if the loading fails:

+ if privValidator == nil {
+     return fmt.Errorf("failed to load private validator")
+ }

Committable suggestion was skipped due to low confidence.

@@ -131,7 +140,7 @@
Use: "show-address",
Short: "Shows this node's CometBFT validator consensus address",
RunE: func(cmd *cobra.Command, args []string) error {
cfg := s.config.CmtConfig
cfg := client.GetConfigFromCmd(cmd)
Copy link
Contributor

Choose a reason for hiding this comment

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

Consider adding detailed error handling for address conversion in ShowAddressCmd.

The conversion of the validator address to a string is straightforward but does not account for potential issues in the address format or conversion process. Adding error handling could improve robustness:

+ if valConsAddr == nil {
+     return fmt.Errorf("invalid validator consensus address")
+ }
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
cfg := client.GetConfigFromCmd(cmd)
cfg := client.GetConfigFromCmd(cmd)
+ if valConsAddr == nil {
+ return fmt.Errorf("invalid validator consensus address")
+ }

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.

lgtm

if err != nil {
return nil, err
}
return client, nil
}

if s.Node == nil || cmd.Flags().Changed(flags.FlagNode) {
rpcURI, _ := cmd.Flags().GetString(flags.FlagNode)
Copy link
Contributor

Choose a reason for hiding this comment

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

since we can return an error here i would not silent ignore it; even though it's unlikely to happen due to line above

@hieuvubk hieuvubk enabled auto-merge June 12, 2024 18:14
@hieuvubk hieuvubk disabled auto-merge June 12, 2024 18:14
@hieuvubk hieuvubk enabled auto-merge June 12, 2024 18:22
@hieuvubk hieuvubk added this pull request to the merge queue Jun 12, 2024
Merged via the queue into main with commit 8d205af Jun 12, 2024
62 of 64 checks passed
@hieuvubk hieuvubk deleted the hieu/comet_commands branch June 12, 2024 18:31
alpe added a commit that referenced this pull request Jun 13, 2024
* main:
  fix(x/staking): stop validators from rotating to the same key on the same block (#20649)
  perf: add cache to address codec (#20122)
  build(deps): Bump google.golang.org/protobuf from 1.34.1 to 1.34.2 (#20632)
  fix: remove recipient amount from map (#20625)
  fix(proto): remove conditional preventing proper generated file placement (#20650)
  (serverv2/cometbft) Read config from commands & handle `FlagNode` (#20621)
  fix(x/consensus): fix .proto file placement (#20646)
  fix(store): avoid nil error on not exhausted payload stream (#20644)
  fix (x/accounts): Fix genesis condition check (#20645)
  feat(accounts): add genesis account initialization (#20642)
  fix(x/gov): limit execution in gov (#20348)
@julienrbrt julienrbrt changed the title (serverv2/cometbft) Read config from commands & handle FlagNode feat(serverv2/cometbft) Read config from commands & handle FlagNode Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

(serverv2) CometServer commands should not rely on nested structure inside
4 participants