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: overwrite default cometbft timeout_commit #438

Merged
merged 2 commits into from
Dec 4, 2024
Merged

Conversation

boojamya
Copy link
Member

@boojamya boojamya commented Dec 3, 2024

This PR overwrites the cometbft default timeout_commit from 5s to 500ms.
You will be able to see this change take effect when initializing Noble (nobled init).

For context, 500ms is what the current Noble validator set has manually adjusted in the config.toml file.

@boojamya boojamya requested a review from a team as a code owner December 3, 2024 19:25
Copy link

coderabbitai bot commented Dec 3, 2024

Walkthrough

The changes in this pull request involve modifications to the cmd/root.go file and the local.sh script. In cmd/root.go, a new timeout configuration for the cometbft setup is introduced, setting the TimeoutCommit to 500 milliseconds. The local.sh script is updated to enhance the initialization of the nobled application, including adding new token metadata to the genesis configuration and adjusting key parameters related to token minting and staking. A specific timeout adjustment in the config.toml file has also been removed.

Changes

File Change Summary
cmd/root.go Added import for time, established TimeoutCommit parameter in PersistentPreRunE with 500ms.
local.sh Updated genesis configuration with new token metadata, initialized validator, adjusted minting and bond denom, and removed timeout adjustment in config.toml.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Cmd
    participant Config

    User->>Cmd: Execute command
    Cmd->>Config: Load default configuration
    Config-->>Cmd: Return config
    Cmd->>Config: Set TimeoutCommit to 500ms
    Cmd->>User: Command execution complete
Loading

🐇 "In the meadow, changes bloom,
New tokens dance, dispelling gloom.
With timing set to half a sec,
Our app's now sharp, what the heck!
Hopping forth with joy and cheer,
A brighter future, oh so near!" 🌼


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 912f83f and e1a1b34.

📒 Files selected for processing (1)
  • cmd/root.go (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • cmd/root.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.

CodeRabbit Configuration 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

@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

🧹 Outside diff range and nitpick comments (1)
cmd/root.go (1)

75-77: Consider improving maintainability

While the implementation is correct, consider these improvements:

  1. Add a comment explaining why 500ms was chosen
  2. Consider making the timeout value a constant for easier future modifications
+// DefaultTimeoutCommit represents the standard block commit timeout across validators
+const DefaultTimeoutCommit = 500 * time.Millisecond
+
 // overwrite default timeout_commit from the cometbft configuration
 cmtCfg := cmtcfg.DefaultConfig()
-cmtCfg.Consensus.TimeoutCommit = (500 * time.Millisecond)
+// Set to 500ms to align with existing validator configurations
+cmtCfg.Consensus.TimeoutCommit = DefaultTimeoutCommit
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3186b2b and 912f83f.

📒 Files selected for processing (2)
  • cmd/root.go (2 hunks)
  • local.sh (0 hunks)
💤 Files with no reviewable changes (1)
  • local.sh
🔇 Additional comments (2)
cmd/root.go (2)

18-18: LGTM: Required import for duration configuration

The addition of the time package is necessary for setting the TimeoutCommit duration.


75-77: Implementation aligns with PR objective

The change correctly implements the 500ms TimeoutCommit configuration, matching the existing validator configurations. However, let's verify this change doesn't affect other parts of the system.

✅ Verification successful

The previous command failed because it was restricted to .toml files which might not exist. Let's broaden the search to all files and also check what config files exist in the repository.


Let's verify if there are any related timeout configurations in the app.yaml or other consensus timeout settings that might be affected by this change.


TimeoutCommit configuration change is safe to implement

The verification shows that:

  1. The TimeoutCommit configuration is only set in cmd/root.go
  2. No conflicting timeout configurations exist in app.yaml or other configuration files
  3. No other consensus timeout settings will be affected by this change
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any other timeout_commit configurations that might conflict
rg -i "timeout.?commit" --type toml

Length of output: 186


Script:

#!/bin/bash
# Search for any timeout_commit configurations in all files
rg -i "timeout.?commit"

# Also check for any config files that might have different extensions
fd -e yaml -e toml -e json -e conf

Length of output: 227


Script:

#!/bin/bash
# Let's check the content of app.yaml for any timeout configurations
cat app.yaml

# Also search for any other consensus timeout related configurations
rg -i "consensus.*timeout"

Length of output: 4135

johnletey
johnletey previously approved these changes Dec 4, 2024
Copy link
Member

@johnletey johnletey left a comment

Choose a reason for hiding this comment

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

Easy approval, just left two small nits @boojamya 😄

cmd/root.go Outdated Show resolved Hide resolved
cmd/root.go Outdated Show resolved Hide resolved
@johnletey johnletey changed the title feat: overwrite default comebft timeout_commit chore: overwrite default cometbft timeout_commit Dec 4, 2024
@boojamya boojamya merged commit 720ab6f into main Dec 4, 2024
37 checks passed
@boojamya boojamya deleted the dan/timeout-commit branch December 4, 2024 14:52
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.

2 participants