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

Problem: iavl v1 pruning takes a long time #1692

Merged
merged 6 commits into from
Nov 14, 2024

Conversation

yihuang
Copy link
Collaborator

@yihuang yihuang commented Nov 13, 2024

Solution:

  • set async pruning option

👮🏻👮🏻👮🏻 !!!! REFERENCE THE PROBLEM YOUR ARE SOLVING IN THE PR TITLE AND DESCRIBE YOUR SOLUTION HERE !!!! DO NOT FORGET !!!! 👮🏻👮🏻👮🏻

PR Checklist:

  • Have you read the CONTRIBUTING.md?
  • Does your PR follow the C4 patch requirements?
  • Have you rebased your work on top of the latest master?
  • Have you checked your code compiles? (make)
  • Have you included tests for any non-trivial functionality?
  • Have you checked your code passes the unit tests? (make test)
  • Have you checked your code formatting is correct? (go fmt)
  • Have you checked your basic code style is fine? (golangci-lint run)
  • If you added any dependencies, have you checked they do not contain any known vulnerabilities? (go list -json -m all | nancy sleuth)
  • If your changes affect the client infrastructure, have you run the integration test?
  • If your changes affect public APIs, does your PR follow the C4 evolution of public contracts?
  • If your code changes public APIs, have you incremented the crate version numbers and documented your changes in the CHANGELOG.md?
  • If you are contributing for the first time, please read the agreement in CONTRIBUTING.md now and add a comment to this pull request stating that your PR is in accordance with the Developer's Certificate of Origin.

Thank you for your code, it's appreciated! :)

Summary by CodeRabbit

  • Bug Fixes

    • Resolved issue with no trace detail on insufficient balance.
    • Fixed command for correcting corrupted data in versiondb.
  • Improvements

    • NewKVStore now accepts a string as the store name in versiondb.
    • Introduced a new API for adding timestamps to the versiondb iterator.
    • Added option for IAVL async pruning.
  • Documentation

    • Updated CHANGELOG.md with new entries for bug fixes and improvements.

Solution:
- set async pruning option
@yihuang yihuang requested a review from a team as a code owner November 13, 2024 02:31
@yihuang yihuang requested review from devashishdxt and leejw51crypto and removed request for a team November 13, 2024 02:31
Copy link
Contributor

coderabbitai bot commented Nov 13, 2024

Walkthrough

The pull request includes updates to the CHANGELOG.md and go.mod files. The CHANGELOG.md now documents new bug fixes and improvements, including features in versiondb such as accepting a string as a store name and a new API for timestamps. The go.mod file has been updated for dependency management, including version changes and replacements of several packages, particularly those related to the Cosmos SDK and Ethereum.

Changes

File Change Summary
CHANGELOG.md Updated with new entries under "Bug Fixes" and "Improvements". Added specific bug fixes and new features for versiondb.
go.mod Updated Go module version to go 1.23.1. Added, updated, or replaced several dependencies, including github.com/cosmos/cosmos-sdk.

Possibly related PRs

Suggested reviewers

  • devashishdxt
  • calvinaco
  • mmsqe

🐰 In the code where changes bloom,
New features sprout, dispelling gloom.
Dependencies dance, updated with care,
In the changelog, our progress we share.
Hops of joy for fixes and more,
A brighter future we all explore! 🌟

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 golangci-lint

level=warning msg="The linter 'exportloopref' is deprecated (since v1.60.2) due to: Since Go1.22 (loopvar) this linter is no longer relevant. Replaced by copyloopvar."


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 37d443f and ab8573c.

⛔ Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (1)
  • go.mod (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • go.mod

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.

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

@yihuang yihuang requested a review from mmsqe November 13, 2024 02:33
CHANGELOG.md Outdated Show resolved Hide resolved
Signed-off-by: yihuang <[email protected]>
Copy link

codecov bot commented Nov 13, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 31.19%. Comparing base (f1ee213) to head (ab8573c).
Report is 1 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##             main    #1692       +/-   ##
===========================================
+ Coverage   16.87%   31.19%   +14.31%     
===========================================
  Files          72      120       +48     
  Lines        6163    11718     +5555     
===========================================
+ Hits         1040     3655     +2615     
- Misses       5000     7731     +2731     
- Partials      123      332      +209     

see 92 files with indirect coverage changes

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 (2)
go.mod (2)

Line range hint 3-3: Invalid Go version specified

The Go version 1.23.1 does not exist. The latest stable version is 1.22.1. This will cause build failures.

Apply this diff to fix the version:

-go 1.23.1
+go 1.22

Line range hint 275-277: Track security-related TODOs

There are multiple TODO comments referencing security-related issues that need tracking:

  1. Removal of deprecated jwt-go package
  2. Fixing upstream vulnerabilities in gin-gonic/gin

Would you like me to create GitHub issues to track these security-related TODOs?

Also applies to: 279-280

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 6dc645a and 37d443f.

⛔ Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • go.mod (1 hunks)
🔇 Additional comments (3)
go.mod (2)

Line range hint 108-108: Verify IAVL version compatibility with async pruning

The IAVL version is pinned to a specific commit from the release/v1.2.x branch. Let's verify if this version includes the async pruning feature.


257-257: Verify Cosmos SDK fork compatibility

The PR updates to a specific commit of the crypto-org-chain's Cosmos SDK fork. Let's verify the changes in this fork.

✅ Verification successful

Cosmos SDK fork compatibility confirmed

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check the changes in the Cosmos SDK fork

# Get the commit message and changes
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/crypto-org-chain/cosmos-sdk/commits/e790d2346678 \
  --jq '.commit.message'

# Check for breaking changes
rg -l "BREAKING CHANGE" 

Length of output: 487


Script:

#!/bin/bash
# Description: Check for indicators of breaking changes in the Cosmos SDK fork commit

# Search the commit message for 'BREAKING CHANGE' or similar indicators
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/crypto-org-chain/cosmos-sdk/commits/e790d2346678 \
  --jq '.commit.message' | rg -i "BREAKING CHANGE|significant change|major update"

Length of output: 183

CHANGELOG.md (1)

14-14: LGTM!

The changelog entry is well-formatted, correctly references PR #1692, and accurately describes the change to implement async pruning for IAVL v1.

Copy link
Collaborator

@mmsqe mmsqe left a comment

Choose a reason for hiding this comment

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

just not sure if we need PausePruning with AsyncPruning since it's only used after sdk 52.x

@yihuang yihuang marked this pull request as draft November 13, 2024 03:18
@yihuang yihuang force-pushed the async-pruning branch 2 times, most recently from 5554c85 to bb41758 Compare November 13, 2024 07:20
@yihuang yihuang marked this pull request as ready for review November 14, 2024 02:10
@mmsqe mmsqe added this pull request to the merge queue Nov 14, 2024
Merged via the queue into crypto-org-chain:main with commit 93a1ed7 Nov 14, 2024
36 checks passed
@yihuang yihuang deleted the async-pruning branch November 14, 2024 04:05
@coderabbitai coderabbitai bot mentioned this pull request Nov 14, 2024
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants