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(x): add module_query_safe on queries #22095

Closed
wants to merge 8 commits into from
Closed

Conversation

Teyz
Copy link
Contributor

@Teyz Teyz commented Oct 3, 2024

Description

Closes: #20219


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

  • New Features

    • Introduced new functionalities in the x/distribution and x/gov modules, including custom tally functions and support for multiple choice proposals.
  • Improvements

    • Enhanced query safety with the addition of module_query_safe for various RPC methods.
    • Removed dependencies on x/protocolpool for token transfers in the x/distribution module.
  • Bug Fixes

    • Addressed a vulnerability in the incrementReferenceCount method within the x/distribution module.
  • Breaking Changes

    • Significant modifications to API and CLI methods in both x/distribution and x/gov modules, including changes to method signatures and removal of deprecated features.

Copy link
Contributor

coderabbitai bot commented Oct 3, 2024

📝 Walkthrough
📝 Walkthrough
📝 Walkthrough
📝 Walkthrough

Walkthrough

The pull request updates the changelogs and proto files for the x/distribution and x/gov modules. Key changes include the addition of the module_query_safe option to various RPC methods, modifications to method signatures to accept string arguments instead of specific address types, and the removal of certain methods and dependencies. The changelog entries summarize significant features, improvements, and breaking changes across both modules, reflecting a substantial evolution in their functionality and API.

Changes

File Change Summary
x/distribution/CHANGELOG.md Updated to include new features, improvements, API breaking changes, CLI breaking changes, state machine breaking changes, client breaking changes, and bug fixes in the x/distribution module.
x/distribution/proto/cosmos/distribution/v1beta1/query.proto Added module_query_safe option to multiple RPC methods and marked CommunityPool as deprecated. Added import for cosmos/query/v1/query.proto.
x/gov/CHANGELOG.md Updated to reflect new features, improvements, and breaking changes in the x/gov module, including the introduction of new methods and significant modifications to existing method signatures.
x/gov/proto/cosmos/gov/v1beta1/query.proto Added module_query_safe option to several RPC methods and included an import for cosmos/query/v1/query.proto.

Assessment against linked issues

Objective Addressed Explanation
Mark all x/distribution queries with module_query_safe (20219)
Mark all x/gov queries with module_query_safe (20219)

Possibly related PRs

Suggested labels

C:x/bank, C:x/staking, C:x/auth, C:x/circuit, backport/v0.52.x

Suggested reviewers

  • sontrinh16
  • kocubinski
  • julienrbrt
  • testinginprod

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.

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.

@github-actions github-actions bot added the C:x/distribution distribution module related label Oct 3, 2024
@Teyz Teyz marked this pull request as ready for review October 3, 2024 13:58
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.

You need to run make proto-gen to regenerate the protos

@julienrbrt
Copy link
Member

julienrbrt commented Oct 3, 2024

For the reviewers, here is the definition of module_query_safe (I had to look it up):
https://github.com/cosmos/cosmos-sdk/blob/main/proto/cosmos/query/v1/query.proto#L11-L36

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

🧹 Outside diff range and nitpick comments (8)
x/distribution/CHANGELOG.md (5)

33-33: Remove or populate the empty bullet point in the Features section.

An empty bullet point doesn't provide any information to the readers. Either remove this line or add details about a new feature introduced in this version.


35-36: Improvements section looks good, minor formatting suggestion.

The new entries in the Improvements section are clear and informative. The second entry directly addresses the PR objective of marking more queries with module_query_safe.

For consistency, consider using the same formatting for both entries:

* [#20790](https://github.com/cosmos/cosmos-sdk/pull/20790) `x/distribution` does not depend on `x/protocolpool` anymore, now `x/distribution` only does token transfers and `x/protocolpool` does the rest.
* [#20219](https://github.com/cosmos/cosmos-sdk/issues/20219) Mark more queries with `module_query_safe`.

Line range hint 38-63: API Breaking Changes section is comprehensive, minor suggestion for clarity.

The API Breaking Changes section provides detailed information about the changes, which is crucial for developers. The entries align well with the PR objectives and the AI-generated summary.

To improve clarity, consider grouping related changes together. For example, you could group all the changes related to the use of collections for state management under a single bullet point with sub-points. This would make it easier for readers to understand the overall direction of the changes.

Example:

* Use of collections for state management:
  * [#17115](https://github.com/cosmos/cosmos-sdk/pull/17115) `PreviousProposer` and `ValidatorSlashEvents`
  * [#16483](https://github.com/cosmos/cosmos-sdk/pull/16483) `DelegatorStartingInfo`
  * [#16571](https://github.com/cosmos/cosmos-sdk/pull/16571) `ValidatorAccumulatedCommission`
  * [#16590](https://github.com/cosmos/cosmos-sdk/pull/16590) `ValidatorOutstandingRewards`
  * [#16607](https://github.com/cosmos/cosmos-sdk/pull/16607) `ValidatorHistoricalRewards`
  * [#16440](https://github.com/cosmos/cosmos-sdk/pull/16440) `DelegatorWithdrawAddresState`
  * [#16459](https://github.com/cosmos/cosmos-sdk/pull/16459) `ValidatorCurrentRewards`

This grouping would make the changelog more readable while still preserving all the necessary information.


Line range hint 71-75: State Machine Breaking section is informative, minor suggestion for consistency.

The State Machine Breaking section provides clear information about significant changes to the state machine. These changes align well with the PR objectives and the AI-generated summary.

For consistency with other sections, consider adding links to the corresponding pull requests for each entry. For example:

* [#20735](https://github.com/cosmos/cosmos-sdk/pull/20735) Remove PreviousProposer from the state machine.
* [#17657](https://github.com/cosmos/cosmos-sdk/pull/17657) Migrate community pool funds from `x/distribution` to `x/protocolpool`.
* [#17115](https://github.com/cosmos/cosmos-sdk/pull/17115) Migrate `PreviousProposer` to collections.
* [#18539](https://github.com/cosmos/cosmos-sdk/pull/18539) Introduce `FeePool.DecimalPool` to replace `FeePool.CommunityPool`, which temporarily holds fractional rewards until they are distributed to the community pool every 1000 blocks.

This would make it easier for readers to find more detailed information about each change if needed.


Line range hint 80-81: Consider adding more details to the Bug Fixes entry.

While it's good to mention the fix for the vulnerability in incrementReferenceCount, providing more context would be helpful for users. Consider adding brief details about:

  1. The nature of the vulnerability (without exposing sensitive information).
  2. Potential impact on users or the system.
  3. Versions affected (if applicable).

This additional information would help users understand the importance of the fix and whether they need to take any action.

x/gov/CHANGELOG.md (1)

49-49: Enhance the changelog entry with more details.

The new entry accurately reflects the PR objectives, but it could benefit from more specificity. Consider expanding it to include:

  1. The specific modules affected (x/distribution and x/gov).
  2. The purpose of marking these queries as module_query_safe (to enable execution by interchain accounts).

Suggested revision:

* [#20219](https://github.com/cosmos/cosmos-sdk/issues/20219#event-14494455201) Mark more queries in `x/distribution` and `x/gov` modules with `module_query_safe` to enable execution by interchain accounts.

This provides more context and aligns closely with the PR objectives.

x/gov/proto/cosmos/gov/v1beta1/query.proto (1)

Line range hint 1-63: Summary: All gov queries successfully marked as module_query_safe

This PR successfully adds the module_query_safe option to all query RPCs in the gov module. These changes align perfectly with the PR objectives, enabling these queries to be executed by interchain accounts. The implementation is consistent across all methods and should significantly enhance the functionality of interchain accounts within the Cosmos ecosystem.

Consider the following suggestions for future improvements:

  1. Update documentation to reflect these changes and their implications for interchain account usage.
  2. Ensure that any client-side code interacting with these RPCs is updated to handle potential changes in behavior.
  3. Consider adding similar changes to other relevant modules to further expand interchain account capabilities.
x/distribution/proto/cosmos/distribution/v1beta1/query.proto (1)

278-278: Consider updating documentation for CommunityPool deprecation

The CommunityPool RPC method and its associated messages have been marked as deprecated. While this is not directly related to the PR objective of adding module_query_safe options, it's an important change that affects the query service.

Consider updating any relevant documentation or guides to reflect this deprecation and to direct users to the x/protocolpool module's CommunityPool RPC method instead.

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between cd2c8ea and f9b56ea.

📒 Files selected for processing (4)
  • x/distribution/CHANGELOG.md (1 hunks)
  • x/distribution/proto/cosmos/distribution/v1beta1/query.proto (3 hunks)
  • x/gov/CHANGELOG.md (1 hunks)
  • x/gov/proto/cosmos/gov/v1beta1/query.proto (2 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
x/distribution/CHANGELOG.md (1)

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

x/gov/CHANGELOG.md (1)

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

🔇 Additional comments (23)
x/distribution/CHANGELOG.md (2)

Line range hint 68-69: CLI Breaking Changes section is clear and informative.

The entry in the CLI Breaking Changes section clearly explains the change in the withdraw-rewards command's behavior and provides information about the new command for withdrawing validator commission. This is an important breaking change that users need to be aware of, and it's documented well.


Line range hint 77-78: Client Breaking Changes section is clear and helpful.

The entry in the Client Breaking Changes section clearly explains the deprecation of the CommunityPool and FundCommunityPool RPC methods and directs users to the new methods in the x/protocolpool module. This information is crucial for clients using these methods and is documented well.

x/gov/CHANGELOG.md (1)

Line range hint 1-49: Overall changelog structure and content review.

The changelog follows a clear and organized structure, which is commendable. However, there are a few points to consider:

  1. Consistency: Ensure all entries start with a capital letter and end with a period for uniformity.
  2. Versioning: The changes are under the "Unreleased" section. Consider adding a version number if these changes are for a specific upcoming release.
  3. Breaking Changes: The presence of multiple breaking changes sections (State Machine, Client, and API) is good for clarity but ensure all breaking changes are appropriately categorized.
  4. Deprecated Section: Good practice to include this section, but make sure to provide migration paths or alternatives for deprecated features.

Overall, the changelog is well-structured and informative, providing a comprehensive overview of the changes in the x/gov module.

x/gov/proto/cosmos/gov/v1beta1/query.proto (9)

9-9: LGTM: Import added for module_query_safe option

The addition of this import is necessary and aligns with the PR objective of marking queries as module_query_safe.


18-18: LGTM: Proposal query marked as module_query_safe

This change enables the Proposal query to be executed by interchain accounts, aligning with the PR objective.


24-24: LGTM: Proposals query marked as module_query_safe

This change enables the Proposals query to be executed by interchain accounts, aligning with the PR objective.


31-31: LGTM: Vote query marked as module_query_safe

This change enables the Vote query to be executed by interchain accounts, aligning with the PR objective.


37-37: LGTM: Votes query marked as module_query_safe

This change enables the Votes query to be executed by interchain accounts, aligning with the PR objective.


43-43: LGTM: Params query marked as module_query_safe

This change enables the Params query to be executed by interchain accounts, aligning with the PR objective.


49-49: LGTM: Deposit query marked as module_query_safe

This change enables the Deposit query to be executed by interchain accounts, aligning with the PR objective.


55-55: LGTM: Deposits query marked as module_query_safe

This change enables the Deposits query to be executed by interchain accounts, aligning with the PR objective.


61-61: LGTM: TallyResult query marked as module_query_safe

This change enables the TallyResult query to be executed by interchain accounts, aligning with the PR objective.

x/distribution/proto/cosmos/distribution/v1beta1/query.proto (11)

10-10: LGTM: Import added for module_query_safe option

The addition of import "cosmos/query/v1/query.proto"; is correct and necessary for using the module_query_safe option in the RPC methods.


19-19: LGTM: module_query_safe option added to Params RPC

The addition of option (cosmos.query.v1.module_query_safe) = true; to the Params RPC method is correct and aligns with the PR objective of enabling these queries to be executed by interchain accounts.


26-26: LGTM: module_query_safe option added to ValidatorDistributionInfo RPC

The addition of option (cosmos.query.v1.module_query_safe) = true; to the ValidatorDistributionInfo RPC method is correct and consistent with the PR objective.


33-33: LGTM: module_query_safe option added to ValidatorOutstandingRewards RPC

The addition of option (cosmos.query.v1.module_query_safe) = true; to the ValidatorOutstandingRewards RPC method is correct and consistent with the PR objective.


40-40: LGTM: module_query_safe option added to ValidatorCommission RPC

The addition of option (cosmos.query.v1.module_query_safe) = true; to the ValidatorCommission RPC method is correct and consistent with the PR objective.


47-47: LGTM: module_query_safe option added to ValidatorSlashes RPC

The addition of option (cosmos.query.v1.module_query_safe) = true; to the ValidatorSlashes RPC method is correct and consistent with the PR objective.


53-53: LGTM: module_query_safe option added to DelegationRewards RPC

The addition of option (cosmos.query.v1.module_query_safe) = true; to the DelegationRewards RPC method is correct and consistent with the PR objective.


61-61: LGTM: module_query_safe option added to DelegationTotalRewards RPC

The addition of option (cosmos.query.v1.module_query_safe) = true; to the DelegationTotalRewards RPC method is correct and consistent with the PR objective.


67-67: LGTM: module_query_safe option added to DelegatorValidators RPC

The addition of option (cosmos.query.v1.module_query_safe) = true; to the DelegatorValidators RPC method is correct and consistent with the PR objective.


74-74: LGTM: module_query_safe option added to DelegatorWithdrawAddress RPC

The addition of option (cosmos.query.v1.module_query_safe) = true; to the DelegatorWithdrawAddress RPC method is correct and consistent with the PR objective.


Line range hint 1-278: Summary: module_query_safe options added and CommunityPool deprecated

This PR successfully adds the module_query_safe option to all relevant RPC methods in the distribution module's query service. These changes align with the objective of enabling these queries to be executed by interchain accounts.

Key points:

  1. The necessary import for the module_query_safe option has been added.
  2. All relevant RPC methods now include the module_query_safe option.
  3. The CommunityPool RPC method and its associated messages have been deprecated, with a suggestion to use the x/protocolpool module's CommunityPool RPC method instead.

These changes enhance the functionality of the distribution module within the Cosmos SDK ecosystem, particularly for interchain operations. The deprecation of the CommunityPool elements should be noted for future updates to documentation and client implementations.

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

🧹 Outside diff range and nitpick comments (1)
api/cosmos/gov/v1beta1/query.pulsar.go (1)

Line range hint 1-1000: Add license header.

The file is missing a license header. Please add the appropriate license header at the top of the file.

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between f9b56ea and 87eca97.

⛔ Files ignored due to path filters (2)
  • x/distribution/types/query.pb.go is excluded by !**/*.pb.go
  • x/gov/types/v1beta1/query.pb.go is excluded by !**/*.pb.go
📒 Files selected for processing (4)
  • api/cosmos/distribution/v1beta1/query.pulsar.go (3 hunks)
  • api/cosmos/gov/v1beta1/query.pulsar.go (2 hunks)
  • x/distribution/proto/cosmos/distribution/v1beta1/query.proto (3 hunks)
  • x/gov/proto/cosmos/gov/v1beta1/query.proto (2 hunks)
🔥 Files not summarized due to errors (1)
  • api/cosmos/distribution/v1beta1/query.pulsar.go: Error: Server error: no LLM provider could handle the message
🚧 Files skipped from review as they are similar to previous changes (2)
  • x/distribution/proto/cosmos/distribution/v1beta1/query.proto
  • x/gov/proto/cosmos/gov/v1beta1/query.proto
🧰 Additional context used
📓 Path-based instructions (2)
api/cosmos/distribution/v1beta1/query.pulsar.go (1)

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

api/cosmos/gov/v1beta1/query.pulsar.go (1)

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

🔇 Additional comments (6)
api/cosmos/distribution/v1beta1/query.pulsar.go (4)

Line range hint 1-10623: Summary of changes in query.pulsar.go

The modifications in this file align with the PR objectives of marking additional queries with the module_query_safe tag. The changes include:

  1. Adding a new import for the cosmos query package.
  2. Modifications to the generated protobuf code.
  3. Updates to RPC methods with the module_query_safe tag.

These changes appear to be correct and consistent with the PR goals. However, as this is a generated file, please ensure that:

  1. The corresponding .proto files have been updated appropriately.
  2. The new import is being utilized in the codebase.
  3. All intended queries have been marked with the module_query_safe tag.

As a final check, run the following command to ensure all intended queries are tagged:

#!/bin/bash
# List all RPC methods and check for module_query_safe tag
sed -n '/rpc/,/}/p' api/cosmos/distribution/v1beta1/query.pulsar.go | grep -E 'rpc|module_query_safe'

10572-10623: RPC methods updated with module_query_safe tag.

The changes add the module_query_safe tag to several RPC methods in the distribution module. This aligns with the PR objectives to enable these queries to be executed by interchain accounts.

To verify the consistency of these changes:

#!/bin/bash
# Check for the addition of module_query_safe tags in the file
grep -n "module_query_safe" api/cosmos/distribution/v1beta1/query.pulsar.go

8-8: New import added for cosmos query package.

The addition of _ "cosmossdk.io/api/cosmos/query/v1" as a blank import suggests new query functionality might have been added. This looks good, but ensure it's being used in the code.

To verify the usage of this import, run the following command:

✅ Verification successful

Blank import _ "cosmossdk.io/api/cosmos/query/v1" is used consistently for side effects.

The addition of _ "cosmossdk.io/api/cosmos/query/v1" aligns with existing patterns in the codebase, indicating it's necessary for initializing query-related functionalities. No issues found.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for usage of the newly imported package
grep -R "cosmos/query/v1" .

Length of output: 1829


Line range hint 10275-10623: Changes in generated protobuf code.

This section contains modifications to the generated protobuf code. As this is auto-generated, direct edits are not recommended. Please ensure that these changes correspond to modifications in the source .proto files.

To verify the changes, compare the .proto files:

api/cosmos/gov/v1beta1/query.pulsar.go (2)

Line range hint 32-38: LGTM!

The QueryProposalRequest message definition looks good.


Line range hint 32-38: Verify the error handling.

The error handling looks correct. However, please verify that the error message "Vectors must have the same length" is appropriate and provides enough context for the user to understand and fix the issue.

@@ -4,6 +4,7 @@ package govv1beta1
import (
_ "cosmossdk.io/api/amino"
v1beta1 "cosmossdk.io/api/cosmos/base/query/v1beta1"
_ "cosmossdk.io/api/cosmos/query/v1"
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Remove unused import.

The _ "cosmossdk.io/api/cosmos/query/v1" import is unused and can be removed.

@Teyz Teyz requested a review from julienrbrt October 3, 2024 15:19
@alpe
Copy link
Contributor

alpe commented Oct 17, 2024

Going though all queries in gov and distribution to check for deterministic behaviour is some work.

@Teyz can you confirm that you did that before opening the PR?

@Teyz
Copy link
Contributor Author

Teyz commented Oct 29, 2024

Yep

@Teyz
Copy link
Contributor Author

Teyz commented Nov 2, 2024

Can we merge this PR?

@julienrbrt
Copy link
Member

Can we merge this PR?

Hey! It needs to be throughly reviewed first.

Copy link
Contributor

github-actions bot commented Dec 3, 2024

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale label Dec 3, 2024
@github-actions github-actions bot closed this Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C:x/distribution distribution module related C:x/gov Stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Mark more queries with module_query_safe
5 participants