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

Bump github.com/cometbft/cometbft to v0.38.10 (from 0.38.10-pio-1). #2097

Merged
merged 4 commits into from
Jul 19, 2024

Conversation

SpicyLemon
Copy link
Contributor

@SpicyLemon SpicyLemon commented Jul 17, 2024

Description

This PR bumps github.com/cometbft/cometbft to v0.38.10 (from v0.38.10-pio-1).

We forked cometbft and tagged v0.38.10-pio-1 at c2405cc8f: "feat: do not start indexer service (back port: #3331) (#3496)" because we needed some fixes that had been applied to v0.38.x, but hadn't yet been part of a release.

The only difference between v0.38.10-pio-1 and v0.38.10 is 5f59b42: "chore: release v0.38.10 (#3515)". The only thing in that commit/PR that isn't changelog changes, is an update to the version number (which gets reported in stuff like provenanced status).

I fired up a testnet node at 23564251 and let it catch up, then run normally for the evening; it's just hit 23590370 as I'm writing this. So I'm pretty confident that this is not a state-breaking change.

The only real change that this PR makes is that version string. Other than that, this PR is mostly just to get us off of the fork and back onto the primary libary.


Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

  • Targeted PR against correct branch (see CONTRIBUTING.md)
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Wrote unit and integration tests
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/)
  • Added relevant godoc comments.
  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Re-reviewed Files changed in the Github PR explorer
  • Review Codecov Report in the comment section below once CI passes

Summary by CodeRabbit

  • Dependencies

    • Updated github.com/cometbft/cometbft to version v0.38.10.
    • Replaced github.com/cosmos/cosmos-sdk with github.com/provenance-io/cosmos-sdk at version v0.50.7-pio-1.
  • Configuration

    • Updated internal configuration settings for versioning and block creation intervals.

@SpicyLemon SpicyLemon requested a review from a team as a code owner July 17, 2024 16:02
Copy link
Contributor

coderabbitai bot commented Jul 17, 2024

Walkthrough

The recent updates primarily focus on dependency upgrades and configuration changes. The notable updates include bumping the version of the cometbft library and removing a temporary replace directive. Additionally, configuration parameters in the config_test.go file have been adjusted to align with these new dependencies.

Changes

File Change Summary
CHANGELOG.md Updated the cometbft dependency version from v0.38.10-pio-1 to v0.38.10.
go.mod Incremented cometbft version from v0.38.9 to v0.38.10 and replaced cosmos-sdk with provenance-io/cosmos-sdk.
cmd/provenanced/cmd/config_test.go Updated cometbft version, changed blocksync.version, and set consensus.create_empty_blocks_interval to "0s".

Poem

In the code where changes bloom,
Dependencies dance and configurations groom,
Cometbft takes a leap,
Cosmos replaced, no promises to keep.
Empty blocks now wait,
Zero seconds, no debate.
Progress marches on in stride,
With each commit, code's our pride.


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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4ded367 and ac9d354.

Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • go.mod (2 hunks)
Files skipped from review due to trivial changes (1)
  • go.mod
Additional context used
Markdownlint
CHANGELOG.md

46-46: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)

Additional comments not posted (1)
CHANGELOG.md (1)

46-46: Update on Dependency Version in Changelog

The changelog correctly documents the update of the github.com/cometbft/cometbft dependency from version v0.38.10-pio-1 to v0.38.10. This aligns with the summary provided, ensuring the changelog is accurate and up-to-date.

Tools
Markdownlint

46-46: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)

iramiller
iramiller previously approved these changes Jul 17, 2024
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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between ac9d354 and 6a60ad0.

Files selected for processing (1)
  • cmd/provenanced/cmd/config_test.go (1 hunks)
Additional comments not posted (4)
cmd/provenanced/cmd/config_test.go (4)

Line range hint 36-68: Review of SetupTest Function:

The SetupTest function properly sets up the test environment by configuring directories, logging, and default settings. It uses safe practices for directory creation (s.T().TempDir()) and disables address caching which is a good practice for isolated test cases.

However, consider handling potential errors from pioconfig.SetProvenanceConfig and provconfig.DefaultKeyringBackend to ensure that the test setup does not proceed with misconfigured settings.


Line range hint 97-103: Review of getConfigCmd Function:

The getConfigCmd function correctly initializes the configuration command and ensures that the configuration is loaded from files without errors. This is crucial for ensuring that subsequent tests run with the expected setup.

Consider adding more detailed error handling or logging within provconfig.LoadConfigFromFiles to provide clearer diagnostics in case of configuration load failures.


Line range hint 319-341: Review of TestConfigBadArgs Function:

The TestConfigBadArgs function effectively tests various error scenarios for configuration commands, ensuring that the system behaves as expected under erroneous conditions. Each test case is clearly defined and asserts specific error messages, which is good for maintainability and understanding test coverage.

Consider adding a few more edge cases if applicable, such as testing with excessively long strings or special characters to further ensure the robustness of the command parsing.


Line range hint 497-526: Review of TestConfigSetValidation Function:

The TestConfigSetValidation function thoroughly tests the validation mechanisms for different configuration settings. It ensures that invalid settings are correctly identified and rejected, which is crucial for maintaining system integrity.

It would be beneficial to expand the test coverage to include additional configuration parameters, particularly new or complex ones introduced in recent updates, to ensure comprehensive validation.

@SpicyLemon SpicyLemon merged commit 08aff56 into main Jul 19, 2024
32 checks passed
@SpicyLemon SpicyLemon deleted the dwedul/bump-comet-to-10 branch July 19, 2024 12:51
SpicyLemon added a commit that referenced this pull request Jul 19, 2024
…2097)

* Get rid of the cometbft replace and bump it to v0.38.10 (from v0.38.9).

* Add changelog entry.

* Fix changelog entry.

* Fix the config test that broke because it has the comet version number in it that just changed.
SpicyLemon added a commit that referenced this pull request Jul 19, 2024
…2097) (#2101)

* Get rid of the cometbft replace and bump it to v0.38.10 (from v0.38.9).

* Add changelog entry.

* Fix changelog entry.

* Fix the config test that broke because it has the comet version number in it that just changed.
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.

3 participants