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(server/v2): create v2 subpackage in core #19499

Merged
merged 17 commits into from
Feb 27, 2024

Conversation

tac0turtle
Copy link
Member

Description

Create subpackage for core/appmodule/v2 in cosmossdk.io/core


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

Copy link
Contributor

coderabbitai bot commented Feb 20, 2024

Important

Auto Review Skipped

Auto reviews are disabled on base/target branches other than the default branch. Please add the base/target branch pattern to the list of additional branches to be reviewed in the settings.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository.

To trigger a single review, invoke the @coderabbitai review command.

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-tests for this file.
  • 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 tests 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 from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @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.
  • The JSON schema for the configuration file is available here.
  • 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@tac0turtle tac0turtle changed the title chore(server/v2): create v2 subpackage in core v2 chore(server/v2): create v2 subpackage in core Feb 20, 2024

import "context"

// HasPreBlocker is the extension interface that modules should implement to run
Copy link
Member

Choose a reason for hiding this comment

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

This can be then moved in module.go. Additionally we need to update baseapp.

Copy link
Member Author

Choose a reason for hiding this comment

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

this is a duplicate, baseapp needs the return while the new design uses consensus messages and querying directly from the module

Copy link
Member

Choose a reason for hiding this comment

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

I think in our case, consistency and limiting conflicting apis in better.
Additionally, we cannot have x/upgrade compatible with baseapp and server/v2 if we don't modify in baseapp.
In baseapp, we can update it every pre block instead of checking the returned value.

My point about moving this into core/appmodule/v2/module.go still stand btw

Copy link
Member Author

Choose a reason for hiding this comment

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

gonna remove this and we go with there is no v2 yet

@julienrbrt julienrbrt linked an issue Feb 22, 2024 that may be closed by this pull request
@tac0turtle tac0turtle marked this pull request as ready for review February 23, 2024 07:52
@tac0turtle tac0turtle requested a review from a team as a code owner February 23, 2024 07:52
@github-actions github-actions bot added C:x/staking C:x/gov C:x/distribution distribution module related labels Feb 23, 2024
core/store/database.go Outdated Show resolved Hide resolved
core/store/database.go Outdated Show resolved Hide resolved
}

// NonConsensusStore is a simple key-value store that is used to store non-consensus data.
// Note the non-consensus data is not committed to the blockchain and does not allow iteration
Copy link
Contributor

Choose a reason for hiding this comment

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

We can forbid iteration, although, there is no reason to not support it as it's part of the SS interface and all SS backends support it.

Copy link
Member Author

Choose a reason for hiding this comment

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

I was thinking to keep the supported api simple ourselves we can avoid it. Do you think its a requirement for users?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, I could see cases where you'd want to iterate over state. E.g. iterate over all WASM contracts or something.

Copy link
Member Author

Choose a reason for hiding this comment

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

the user would still be able to iterate just not natively

Copy link
Contributor

Choose a reason for hiding this comment

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

How? What does "not natively" mean?

core/store/database.go Show resolved Hide resolved
tac0turtle and others added 2 commits February 25, 2024 15:31
Co-authored-by: Aleksandr Bezobchuk <[email protected]>
Co-authored-by: Aleksandr Bezobchuk <[email protected]>
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.

new appmodule package lgtm, skipped store -- some build errors due to some missed renaming in types/module/module.go

"context"
)

// HasGenesis defines a custom genesis handling API implementation.
Copy link
Member

@julienrbrt julienrbrt Feb 26, 2024

Choose a reason for hiding this comment

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

What are we going to do about genesis in core v1?
I feel like we should delete if when there is consensus about the api, as we never pushed people to use it.
However, I don't think we agreed on this proposed api yet 👀.

Copy link
Member Author

Choose a reason for hiding this comment

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

leaving a todo here and we can discuss on the server call

@tac0turtle
Copy link
Member Author

going to handle genesis cleanup in a follow up pr

@tac0turtle tac0turtle merged commit a2b4dea into server_modular Feb 27, 2024
31 of 59 checks passed
@tac0turtle tac0turtle deleted the tip/serverv2/appmodulev2 branch February 27, 2024 12:13
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.

[Feature(core)]: appmodule/v2
5 participants