cosmos / interchain-security

Interchain Security is an open sourced IBC application which allows cosmos blockchains to lease their proof-of-stake security to one another.
https://cosmos.github.io/interchain-security/
Other
154 stars 115 forks source link

feat!: added E2E test and docs for ConsumerModificationProposal #1949

Closed insumity closed 3 months ago

insumity commented 4 months ago

Description

Adds E2E test for the ConsumerModificationProposal, as well as docs on how to use this new type of proposal.

Note that the E2E test was introduced in the steps_partial_set_security.go file instead of in a new steps_modify_chain.go file because the modification changes are partial-set security related.


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

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

Summary by CodeRabbit

coderabbitai[bot] commented 3 months ago
Walkthrough ## Walkthrough The changes introduce a new `ConsumerModificationProposal` type across various files, enabling modifications to power shaping parameters and chain types for running consumer chains in the Interchain Security module. This includes updates to documentation, test cases, and workflow configurations to support and test the new proposal type. Additionally, there are several URL updates in the documentation for better accuracy and relevance. ## Changes | File(s) | Change Summary | |---------|----------------| | `.github/workflows/nightly-e2e.yml` | Added new job `partial-set-security-modification-proposal` for setting up Go, checking out LFS objects, and running E2E tests. | | `app/provider/app.go` | Added `ibcproviderclient.ConsumerModificationProposalHandler` to the list of handlers. | | `docs/docs/features/partial-set-security.md`, `docs/docs/features/power-shaping.md`, `docs/docs/features/proposals.md`, `docs/docs/frequently-asked-questions.md` | Introduced tips and details regarding the `ConsumerModificationProposal` for modifying power shaping parameters and transitioning between Top N and Opt-In chains. | | `docs/docs/validators/joining-testnet.md`, `docs/docs/validators/overview.md` | Updated URLs in the documentation to point to the new `main` subdomain for Cosmos SDK and Hub documentation. | | `tests/e2e/actions.go`, `tests/e2e/main.go`, `tests/e2e/state.go`, `tests/e2e/steps_partial_set_security.go`, `tests/e2e/test_driver.go` | Added new types, methods, and test steps for `ConsumerModificationProposal` actions to handle consumer chain modifications in E2E tests. | | `tests/integration/distribution.go` | Added a line to check the equality of `feePoolTokens` with the sum of old and new fee amounts. | | `x/ccv/provider/types/proposal.go` | Corrected a typo in the function comment for `NewConsumerModificationProposal`. | ## Sequence Diagram(s) ```mermaid sequenceDiagram participant User participant CI/CD participant GoSetup participant LFSCheckout participant E2ETests participant ProviderHandler participant TestSuite User->>CI/CD: Commit changes CI/CD->>GoSetup: Setup Go environment CI/CD->>LFSCheckout: Checkout LFS objects CI/CD->>E2ETests: Run E2E tests for `ConsumerModificationProposal` E2ETests->>ProviderHandler: Trigger `ConsumerModificationProposal` handler ProviderHandler->>TestSuite: Execute proposal actions TestSuite->>ProviderHandler: Verify proposal results ProviderHandler->>E2ETests: Return results E2ETests->>CI/CD: Report test outcomes CI/CD->>User: Notify test results ```

Recent review details **Configuration used: .coderabbit.yml** **Review profile: CHILL**
Commits Files that changed from the base of the PR and between dc4b913d13a4774a2fd606d63d96dd2956fb3527 and 0cacc4552fb75952abb69a7fde16c18f09a63759.
Files selected for processing (1) * docs/docs/features/proposals.md (2 hunks)
Additional context used
Path-based instructions (1)
docs/docs/features/proposals.md (1) Pattern `**/*.md`: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness. Please DO NOT report any missing or superfluous newlines, in particular at the end or beginning of files."
LanguageTool
docs/docs/features/proposals.md
[uncategorized] ~113-~113: A comma may be missing after the conjunctive/linking adverb ‘Otherwise’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA) Context: ...ill need to include that `top_N` is 50. Otherwise `top_N` would be set to its default val...
Markdownlint
docs/docs/features/proposals.md
139-139: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces) Trailing spaces --- 145-145: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces) Trailing spaces --- 87-87: Expected: 1; Actual: 2 (MD012, no-multiple-blanks) Multiple consecutive blank lines --- 12-12: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings) Headings should be surrounded by blank lines --- 56-56: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings) Headings should be surrounded by blank lines --- 88-88: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings) Headings should be surrounded by blank lines --- 22-22: null (MD031, blanks-around-fences) Fenced code blocks should be surrounded by blank lines --- 53-53: null (MD031, blanks-around-fences) Fenced code blocks should be surrounded by blank lines --- 69-69: null (MD031, blanks-around-fences) Fenced code blocks should be surrounded by blank lines --- 97-97: null (MD031, blanks-around-fences) Fenced code blocks should be surrounded by blank lines --- 128-128: null (MD031, blanks-around-fences) Fenced code blocks should be surrounded by blank lines --- 141-141: null (MD031, blanks-around-fences) Fenced code blocks should be surrounded by blank lines --- 144-144: null (MD031, blanks-around-fences) Fenced code blocks should be surrounded by blank lines --- 146-146: null (MD031, blanks-around-fences) Fenced code blocks should be surrounded by blank lines --- 153-153: null (MD031, blanks-around-fences) Fenced code blocks should be surrounded by blank lines
Additional comments not posted (1)
docs/docs/features/proposals.md (1)
`88-118`: Expand the `ConsumerModificationProposal` section to include transitioning between Top N and Opt-In chains as suggested. Also, consider adding blank lines around headings for better markdown formatting. ```diff - ## `ConsumerModificationProposal` + + ## `ConsumerModificationProposal` + ``` > Likely invalid or redundant comment.
Tools
LanguageTool
[uncategorized] ~113-~113: A comma may be missing after the conjunctive/linking adverb ‘Otherwise’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA) Context: ...ill need to include that `top_N` is 50. Otherwise `top_N` would be set to its default val...
Markdownlint
88-88: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings) Headings should be surrounded by blank lines --- 97-97: null (MD031, blanks-around-fences) Fenced code blocks should be surrounded by blank lines
--- 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 - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `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 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
sainoe commented 3 months ago

LGTM. Thanks for the work!