PundiAI / fx-core

https://functionx.gitbook.io
Apache License 2.0
21 stars 14 forks source link

refactor(upgrade): use a unified method to delete store keys #737

Closed zakir-code closed 1 week ago

zakir-code commented 1 week ago

Summary by CodeRabbit

coderabbitai[bot] commented 1 week ago

Walkthrough

This pull request introduces several modifications across multiple files to enhance logging, refine context management, and streamline migration processes. Key changes include the integration of a logging package, updates to context creation logic, the introduction of a new key removal function, and the removal of deprecated functions and variables in migration files.

Changes

File Path Change Summary
app/upgrade_test.go Added logging package import and initialized logger in buildApp. Updated context creation logic in newContext. Refactored checkKeysIsDelete function for key deletion verification.
app/upgrades/v8/upgrade.go Introduced removeStoreKeys function for deleting keys from a key-value store. Modified CreateUpgradeHandler to use this function.
x/gov/migrations/v8/migrate.go Removed DeleteOldParamsStore function and marked constants as deprecated.
x/staking/migrations/v8/migrate.go Removed deprecated variables (ValidatorOperatorKey, ConsensusPubKey, ConsensusProcessKey) and the DeleteMigrationValidatorStore function.

Possibly related PRs

Poem

In the code where rabbits hop,
We clean the paths, we never stop.
With logs that shine and keys that flee,
Migrations dance, so wild and free!
Old things gone, new ways to play,
Hooray for changes, hip-hip-hooray! 🐇✨


📜 Recent review details **Configuration used: CodeRabbit UI** **Review profile: CHILL**
📥 Commits Files that changed from the base of the PR and between b4a90e9864d3cf97d8e598d2c2982a9a2fdef504 and 55dcb0fb538df0776046d6d9ac5683104d155113.
📒 Files selected for processing (2) * app/upgrade_test.go (4 hunks) * app/upgrades/v8/upgrade.go (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1) * app/upgrade_test.go
🧰 Additional context used
🔇 Additional comments (4)
app/upgrades/v8/upgrade.go (4)
`30-30`: **LGTM: Unified key removal implemented** The change successfully implements the unified method for deleting store keys as per the PR objective. The `removeStoreKeys` function is correctly used with appropriate arguments. --- `44-44`: **LGTM: Consistent use of unified key removal** The change in `migrationGovCustomParam` is consistent with the PR objective and the previous change in `CreateUpgradeHandler`. The `removeStoreKeys` function is correctly used with appropriate arguments. --- `5-5`: **LGTM: Necessary import added** The addition of the "encoding/hex" import is correct and necessary for its usage in the new `removeStoreKeys` function for logging purposes. --- `50-66`: _:warning: Potential issue_ **Potential resource leak in `removeStoreKeys` function** The implementation of the unified method for deleting store keys is good, but there's a potential issue with resource management: 1. The `defer iterator.Close()` is inside the `deleteFn` closure, which is called in a loop. This could lead to multiple open iterators if there are many keys to process, potentially causing resource exhaustion. 2. This issue was previously flagged in a review comment, but it hasn't been addressed in this version. To fix this, consider moving the `iterator.Close()` call to the end of the `for` loop in `deleteFn`, ensuring each iterator is closed after use. Here's a suggested fix: ```diff func removeStoreKeys(ctx sdk.Context, storeKey *storetypes.KVStoreKey, keys [][]byte) { store := ctx.KVStore(storeKey) deleteFn := func(key []byte) { iterator := storetypes.KVStorePrefixIterator(store, key) - defer iterator.Close() for ; iterator.Valid(); iterator.Next() { store.Delete(iterator.Key()) ctx.Logger().Info("remove store key", "kvStore", storeKey.Name(), "prefix", hex.EncodeToString(key), "key", string(iterator.Key())) } + iterator.Close() } for _, key := range keys { deleteFn(key) } } ```
--- 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 , 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. ### 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](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](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.