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

refactor: move baseapp/AppVersionModifer -> core/app #20361

Merged
merged 8 commits into from May 13, 2024

Conversation

kocubinski
Copy link
Contributor

@kocubinski kocubinski commented May 12, 2024

Description

Moves AppVesrsionModifer to core so that #20320 is not required to import baseapp.


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

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 app version management interface for enhanced performance.
    • Ensured consistent implementation across multiple files.
  • New Features
    • Optimized consensus parameter handling for better application performance and reliability.

@kocubinski kocubinski requested a review from a team as a code owner May 12, 2024 21:00
Copy link
Contributor

coderabbitai bot commented May 12, 2024

Warning

Rate Limit Exceeded

@kocubinski has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 20 minutes and 2 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 a806ec1 and 778a5bd.

Walkthrough

The recent changes entail reorganizing the AppVersionModifier interface by relocating it from the baseapp package to the core/app package. This adjustment aims to streamline the management of the appVersion field for improved integration with the consensus engine. Import paths have been revised, and type declarations updated across various files to align with the new placement of the AppVersionModifier interface.

Changes

Files Change Summary
core/app/app.go Added VersionModifier interface with methods to set and get appVersion.
runtime/module.go, x/upgrade/depinject.go,
x/upgrade/keeper/keeper.go
Updated import paths and type declarations to utilize app.VersionModifier from core/app.

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.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @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

@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.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between ab1dbe1 and 63313c1.
Files selected for processing (5)
  • baseapp/params.go (1 hunks)
  • core/app/app.go (2 hunks)
  • runtime/module.go (2 hunks)
  • x/upgrade/depinject.go (3 hunks)
  • x/upgrade/exported/exported.go (1 hunks)
Files skipped from review due to trivial changes (1)
  • baseapp/params.go
Additional Context Used
Path-based Instructions (4)
x/upgrade/exported/exported.go (1)

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

core/app/app.go (1)

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

x/upgrade/depinject.go (1)

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

runtime/module.go (1)

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

Additional comments not posted (7)
x/upgrade/exported/exported.go (2)

4-4: The updated import path correctly reflects the new location of AppVersionModifier.


11-11: The type declaration is updated to use the new AppVersionModifier from core/app, aligning with the relocation changes.

core/app/app.go (1)

69-76: The definition of AppVersionModifier interface with methods for setting and getting the app version is correctly implemented and aligns with the intended functionality.

x/upgrade/depinject.go (2)

4-4: The import of core/app is correctly added to reflect the new location of AppVersionModifier.


42-42: The update in ModuleInputs struct to use the new AppVersionModifier from core/app is correctly implemented.

runtime/module.go (2)

4-4: The import of core/app is correctly added to reflect the new location of AppVersionModifier.


285-285: The function ProvideAppVersionModifier correctly provides an instance of AppVersionModifier, aligning with the changes made in the relocation of the interface.

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

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between 63313c1 and 3cbeedd.
Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
Additional Context Used
Path-based Instructions (1)
CHANGELOG.md (1)

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

CHANGELOG.md Outdated Show resolved Hide resolved
kocubinski and others added 3 commits May 12, 2024 16:25
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
…smos-sdk into kocu/app-version-modifier-core
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

Out of diff range and nitpick comments (3)
CHANGELOG.md (3)

120-120: Consider specifying the exact new location of AppVersionModifier in the changelog for clarity.


120-120: Clarify how the new argument in SimulateFromSeed affects existing implementations to help users adapt their code.


120-120: It would be beneficial to include information about the impact of removing Address.String() and any alternative methods provided.

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between 3cbeedd and 56f0b51.
Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • x/upgrade/depinject.go (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • x/upgrade/depinject.go
Additional Context Used
Path-based Instructions (1)
CHANGELOG.md (1)

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

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

120-120: This entry clearly describes the change in the function signature. Well documented.

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.

nits + questions

CHANGELOG.md Outdated
@@ -117,6 +117,7 @@ Every module contains its own CHANGELOG.md. Please refer to the module you are i

### API Breaking Changes

* (baseapp) [#20361](https://github.com/cosmos/cosmos-sdk/pull/20361) `AppVersionModifier` moved to `core`.
Copy link
Member

Choose a reason for hiding this comment

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

it was never released but introduced in #16244, so I don't think we need this.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In that case I may also rename to not include the package name app -> VersionModifier

Copy link
Member

Choose a reason for hiding this comment

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

importing core is fine, why do we need this type alias

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point, it was an unthinking refactor

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

Review Details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between 56f0b51 and 5fd1148.
Files selected for processing (4)
  • core/app/app.go (2 hunks)
  • runtime/module.go (2 hunks)
  • x/upgrade/depinject.go (2 hunks)
  • x/upgrade/keeper/keeper.go (3 hunks)
Files skipped from review as they are similar to previous changes (3)
  • core/app/app.go
  • runtime/module.go
  • x/upgrade/depinject.go
Additional Context Used
Path-based Instructions (1)
x/upgrade/keeper/keeper.go (1)

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

Additional comments not posted (1)
x/upgrade/keeper/keeper.go (1)

17-17: The updated import path aligns with the new location of AppVersionModifier. Good job on maintaining consistency.

@@ -36,7 +36,7 @@ type Keeper struct {
skipUpgradeHeights map[int64]bool // map of heights to skip for an upgrade
cdc codec.BinaryCodec // App-wide binary codec
upgradeHandlers map[string]types.UpgradeHandler // map of plan name to upgrade handler
versionModifier xp.AppVersionModifier // implements setting the protocol version field on BaseApp
versionModifier app.VersionModifier // implements setting the protocol version field on BaseApp
Copy link
Contributor

Choose a reason for hiding this comment

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

Tip

Codebase Verification

The type change for versionModifier to app.VersionModifier in the Keeper struct was noted as correctly updated. However, there is still a reference to the old type xp.AppVersionModifier in the codebase:

  • x/upgrade/keeper/keeper.go: The old type is still referenced.

Please ensure that all references to this type are updated accordingly to maintain consistency and avoid potential runtime errors.

Analysis chain

The type change for versionModifier is correctly updated to app.VersionModifier. Ensure all references to this type across the codebase are updated accordingly.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify all references to `AppVersionModifier` have been updated to `app.VersionModifier`.

# Test: Search for the old type usage. Expect: No occurrences of the old type.
rg --type go $'xp.AppVersionModifier'

Length of output: 90

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.yml
Review profile: CHILL

Commits Files that changed from the base of the PR and between 5fd1148 and a806ec1.
Files selected for processing (1)
  • runtime/module.go (2 hunks)
Files skipped from review as they are similar to previous changes (1)
  • runtime/module.go

Copy link
Member

@tac0turtle tac0turtle left a comment

Choose a reason for hiding this comment

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

lgtm. like julien said we can remove the changelog as well. I think there is a cleaner way we can do this as well. something like upgrade sets it on consensus instead of having to go through BaseApp, but that's orthogonal to this pr

@julienrbrt julienrbrt added this pull request to the merge queue May 13, 2024
Merged via the queue into main with commit 9f42137 May 13, 2024
68 of 69 checks passed
@julienrbrt julienrbrt deleted the kocu/app-version-modifier-core branch May 13, 2024 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants