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: recent bug fixes are not included #1690

Merged
merged 6 commits into from
Nov 14, 2024

Conversation

mmsqe
Copy link
Collaborator

@mmsqe mmsqe commented Nov 12, 2024

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

for more info

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 issues with the debug trace API, including balance and gas price adjustments.
    • Added handling for nil pointer panic with the legacy transaction format.
    • Confirmed no trace detail will be provided on insufficient balance.
    • Introduced a command to fix corrupted data in the version database.
  • Improvements

    • Updated the versiondb with enhancements.
    • Introduced a new Timestamp API for the versiondb iterator.
    • Set the IAVL async pruning option.
  • Documentation

    • Updated the CHANGELOG.md to reflect recent changes, including detailed entries for bug fixes and improvements, along with historical entries for version v1.4.0-rc3.

@mmsqe mmsqe requested a review from a team as a code owner November 12, 2024 13:11
@mmsqe mmsqe requested review from yihuang and JayT106 and removed request for a team November 12, 2024 13:11
Copy link
Contributor

coderabbitai bot commented Nov 12, 2024

Walkthrough

The pull request updates the CHANGELOG.md for version v1.4.0-rc4, expanding entries related to bug fixes and improvements, particularly for pull request #1690, which addresses issues with the debug trace API and legacy transaction format. The go.mod file is also modified, reflecting updates to several dependencies, including new paths and versions for various modules, ensuring alignment with the latest sources.

Changes

File Change Summary
CHANGELOG.md - Expanded bug fix entry for PR #1690 to include balance and gas price fix for debug trace API.
- Added new entry for PR #1685 regarding command to fix version database corruption.
- Unchanged entry for PR #1679 confirming no trace detail on insufficient balance.
- Retained previous entries for PR #1684 and #1688, detailing updates in versiondb and new Timestamp API.
- Unchanged entry for PR #1692 on IAVL async pruning option.
go.mod - Updated dependencies and replaced modules:
github.com/99designs/keyringgithub.com/cosmos/keyring
github.com/evmos/ethermintgithub.com/crypto-org-chain/ethermint
github.com/ethereum/go-ethereumgithub.com/crypto-org-chain/go-ethereum
github.com/cometbft/cometbftgithub.com/crypto-org-chain/cometbft
github.com/dgrijalva/jwt-gogithub.com/golang-jwt/jwt/v4
github.com/tidwall/btreegithub.com/crypto-org-chain/btree
cosmossdk.io/storegithub.com/crypto-org-chain/cosmos-sdk/store
cosmossdk.io/x/txgithub.com/crypto-org-chain/cosmos-sdk/x/tx
github.com/cosmos/cosmos-sdkgithub.com/crypto-org-chain/cosmos-sdk.

Possibly related PRs

Suggested reviewers

  • calvinaco
  • devashishdxt
  • yihuang

Poem

🐇 In the changelog, we hop and play,
New fixes and updates brighten the day.
Dependencies shift, like leaves in the breeze,
With each little change, we aim to please!
So let’s celebrate, with a joyful cheer,
For every new feature, brings us near! 🎉


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.

Copy link

codecov bot commented Nov 12, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 11.63%. Comparing base (a3c2f70) to head (4d118aa).
Report is 2 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (a3c2f70) and HEAD (4d118aa). Click for more details.

HEAD has 9 uploads less than BASE
Flag BASE (a3c2f70) HEAD (4d118aa)
integration_tests 10 1
Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1690      +/-   ##
==========================================
- Coverage   16.87%   11.63%   -5.25%     
==========================================
  Files          72       72              
  Lines        6163     6163              
==========================================
- Hits         1040      717     -323     
- Misses       5000     5395     +395     
+ Partials      123       51      -72     

see 15 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: 1

🧹 Outside diff range and nitpick comments (1)
go.mod (1)

Line range hint 3-3: Critical: Invalid Go version specified

The Go version 1.23.1 does not exist (current latest is 1.22.0). This will cause build failures.

Apply this diff to fix the Go version:

-go 1.23.1
+go 1.22.0
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 0c5e998 and 6fc2ca9.

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

Line range hint 5-54: Verify dependency compatibility and security

The dependencies are well-pinned to specific versions or commit hashes, which is good for reproducibility. However, let's verify there are no known vulnerabilities.

#!/bin/bash
# Description: Check for known vulnerabilities in direct dependencies

# Check for security advisories in key dependencies
for pkg in "github.com/ethereum/go-ethereum" "github.com/cosmos/cosmos-sdk" "github.com/cometbft/cometbft"; do
  echo "Checking $pkg..."
  gh api graphql -f query='{
    securityVulnerabilities(first: 5, ecosystem: GO, package: "'$pkg'") {
      nodes {
        advisory {
          summary
          severity
          publishedAt
        }
        vulnerableVersionRange
        firstPatchedVersion {
          identifier
        }
      }
    }
  }'
done

Line range hint 271-275: Verify local module replacements

The local module replacements need to be verified to ensure they exist and are properly structured.

#!/bin/bash
# Description: Verify local module replacements

# Check if the local modules exist and have go.mod files
for dir in "memiavl" "store" "versiondb"; do
  echo "Checking $dir..."
  if [ -d "$dir" ] && [ -f "$dir/go.mod" ]; then
    echo "$dir exists and has go.mod"
  else
    echo "$dir is missing or incomplete"
  fi
done
CHANGELOG.md (3)

Line range hint 1-1000: LGTM! The changelog structure is consistent.

The changelog follows a clear and consistent format with:

  • Proper version sections with dates
  • Categorized changes (Bug Fixes, Improvements, etc.)
  • Referenced PR numbers and descriptions

Line range hint 12-13: Verify the improvement entries format and details.

The improvement entries follow the changelog format but should provide more context about:

  1. Why versiondb NewKVStore needed to accept string as store name
  2. The use cases and benefits of the new Timestamp API in versiondb iterator
#!/bin/bash
# Description: Verify the referenced PRs and their changes

# Check PR #1684 details
gh pr view 1684 --json title,body,commits,files

# Check PR #1688 details
gh pr view 1688 --json title,body,commits,files

8-8: Verify the bug fix entry format and details.

The bug fix entry follows the changelog format but should provide more details about:

  1. The specific balance and gas price issues that were fixed
  2. The rationale for checking gasWanted only in checkTx mode

go.mod Outdated Show resolved Hide resolved
mmsqe and others added 2 commits November 14, 2024 15:56
go.mod Show resolved Hide resolved
@yihuang yihuang added this pull request to the merge queue Nov 14, 2024
CHANGELOG.md Outdated Show resolved Hide resolved
@mmsqe mmsqe removed this pull request from the merge queue due to a manual request Nov 14, 2024
@mmsqe mmsqe enabled auto-merge November 14, 2024 09:07
@mmsqe mmsqe added this pull request to the merge queue Nov 14, 2024
Merged via the queue into crypto-org-chain:main with commit ce797fa Nov 14, 2024
35 of 36 checks passed
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