Skip to content

Conversation

@mmsqe
Copy link
Contributor

@mmsqe mmsqe commented Apr 9, 2025

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

for more info:
crypto-org-chain/ethermint@62042e2...434f46d
crypto-org-chain/cometbft@ce418f8...1964da4

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

Summary by CodeRabbit

  • Documentation

    • Updated the release notes to highlight changes for new version releases, including entries for versions v1.4.6, v1.4.5, and v1.4.4.
  • Bug Fixes

    • Resolved issues affecting transaction processing, concurrency, and overall performance for a smoother experience, including fixes for edge cases and version mismatches.
  • Chores

    • Updated core dependencies, including an upgrade to rocksdb and applied a security patch to improve system reliability.

@mmsqe mmsqe requested a review from a team as a code owner April 9, 2025 06:51
@mmsqe mmsqe requested review from thomas-nguy and yihuang and removed request for a team April 9, 2025 06:51
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 9, 2025

Walkthrough

This pull request updates the CHANGELOG.md file by adding new sections and entries corresponding to versions v1.4.6, v1.4.5, and v1.4.4. The changes include listing multiple bug fixes and improvements such as handling an edge case in eth_getLogs, incorporating ethermint bug fixes, upgrading rocksdb to v9.11.2, modifying memiavl LoadVersion behavior, addressing version mismatch issues, applying a security patch from ibc-go, and resolving performance, deadlock, and nonce management issues. The entries are clearly organized with new sections for improvements.

Changes

File Change Summary
CHANGELOG.md - v1.4.6: Added bug fixes for eth_getLogs edge case with batch transactions, ethermint bug fixes; upgraded rocksdb to v9.11.2; updated memiavl LoadVersion to load up to the target version.
- v1.4.5: Added fixes for occasional version mismatches and included a security patch from ibc-go; repeated the memiavl LoadVersion improvement.
- v1.4.4: Added fixes for iavl performance regressions, deadlock on tree closure, and nonce management in batch transactions.
go.mod Updated github.com/cometbft/cometbft dependency version from v0.0.0-20241106091515-ce418f845d9a to v0.0.0-20250203071505-1964da4a0cac and updated github.com/evmos/ethermint version from v0.6.1-0.20250109075157-62042e2252f6 to v0.6.1-0.20250409022716-434f46d2a46c, modifying the comment from // release/v1.4.x to // release/v1.4.x-2.
gomod2nix.toml Updated github.com/cometbft/cometbft version from v0.0.0-20241106091515-ce418f845d9a to v0.0.0-20250203071505-1964da4a0cac and changed the hash value from sha256-Eu9HQ7EfyU7/+2DL/aDVHlOwJhtdX2pPHDG/mGI7KyI= to sha256-69eQmjbxHnnXXC4wAVUFVY031fRzUSGeqbemzWylgzI=. Similarly, updated github.com/evmos/ethermint version from v0.6.1-0.20250109075157-62042e2252f6 to v0.6.1-0.20250409022716-434f46d2a46c and changed the hash from sha256-ZmkYPzUBw0pZyoYFckKMq6/yEdtVfWuV7XvEWxycMWg= to sha256-4dIcLX/qbcgSdXwlcWALJFM+BsnmyL3y+ybqDsT14Ls=.

Possibly related PRs

  • Problem: cometbft not up to date #1568: The changes in the main PR and the retrieved PR are related as both involve updates to the CHANGELOG.md and modifications to the go.mod file regarding the versioning of the cometbft dependency.
  • Problem: security patch from ibc-go is not included #1766: The changes in the main PR include a new entry for a security patch from ibc-go, which directly relates to the changes made in the retrieved PR that also addresses the inclusion of a security patch from ibc-go.
  • Problem: rocksdb 9.8.4 is not used #1712: The changes in the main PR regarding the upgrade of rocksdb to version v9.11.2 are directly related to the retrieved PR, which also addresses the usage of rocksdb by upgrading it to version v9.8.4. Both PRs involve modifications to the rocksdb dependency, indicating a connection at the code level.

Suggested labels

backport/v1.4.x

Suggested reviewers

  • calvinaco
  • thomas-nguy
  • yihuang

Poem

I'm a rabbit, hopping with delight,
Changelog lines gleam in the code’s night.
Bugs vanish and tweaks now appear,
Each version updated, crystal clear.
With each hop, our code sings true —
A whiskered cheer for all that is new!
🐰✨


🪧 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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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
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

🧹 Nitpick comments (5)
CHANGELOG.md (5)

5-10: Clarify the Unreleased Section and Planned Date

The "UNRELEASED" section now starts with an "### Improvements" header and includes the entry for upgrading rocksdb (line 7) with the date "Apr 9, 2025". Please verify that the planned release date is intentional and clearly differentiated from later released sections. It might help to add context (or a note) indicating that these changes are still upcoming.


11-17: Review v1.4.6 Bug Fixes

In the v1.4.6 section, the bug fixes for eth_getLogs edge case (line 15) and ethermint bug fixes (line 16) are clearly listed. It would be good to double-check that the descriptions precisely reflect the nature of the fixes. Also, consider a minor rephrasing for clarity (e.g. “Fix eth_getLogs edge case in batch transactions”).


24-32: Examine v1.4.5 Bug Fixes and Security Patch

In the v1.4.5 section (lines 26–30), two bug fix entries are added. Consider revising “Fix version mismatch happen occasionally” to a clearer phrasing such as “Fix occasional version mismatches.” Also, note that the security patch entry (line 29) specifies from ibc-go as v8.7.0; please verify that the versioning and punctuation in this entry are consistent with similar entries in other sections.


37-42: Assess v1.4.4 Updates for Consistency

Within the v1.4.4 section, two new entries are marked as changes (lines 39 and 41). One adds support for legacy global AccountNumber and the other includes a security patch from ibc-go. Please ensure that the level of detail and formatting for these entries matches the standards used in other version sections—for example, whether to include patch version details consistently.


47-56: Review v1.4.3 Section Additions

The newly added v1.4.3 section (lines 47–56) includes a bug fix updating cometbft (line 53) with the release date "Dec 19, 2024". Confirm that the introduction of this section fits the project’s changelog structure and that the release dates are accurately aligned with your release schedule.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3701cc2 and 55ad0d8.

📒 Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (1)
CHANGELOG.md (1)

18-23: Validate v1.4.6 Improvements Detail

The improvements subsection in v1.4.6 (lines 18–20) introduces the change to memiavl’s LoadVersion behavior. The description is concise and clear. Please confirm that the phrase “loads up to the target version instead of exact version” accurately conveys the technical change. The release date "Mar 13, 2025" (line 22) fits here, but ensure that its chronological relation with the UNRELEASED section is as intended.

@mmsqe mmsqe changed the title Problem: changelog is outdated Problem: recent bug fixes are not included Apr 9, 2025
@socket-security
Copy link

socket-security bot commented Apr 9, 2025

@codecov
Copy link

codecov bot commented Apr 9, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 35.55%. Comparing base (a3c2f70) to head (60e0d27).
Report is 62 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##             main    #1787       +/-   ##
===========================================
+ Coverage   16.87%   35.55%   +18.67%     
===========================================
  Files          72      127       +55     
  Lines        6163    11963     +5800     
===========================================
+ Hits         1040     4253     +3213     
- Misses       5000     7282     +2282     
- Partials      123      428      +305     

see 71 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@thomas-nguy thomas-nguy changed the title Problem: recent bug fixes are not included Problem: backport v1.4.6 Apr 9, 2025
@thomas-nguy thomas-nguy changed the title Problem: backport v1.4.6 Problem: v1.4.6 is not backported Apr 9, 2025
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

🧹 Nitpick comments (4)
CHANGELOG.md (4)

5-10: New UNRELEASED Improvements Section Added

The new improvements entry for upgrading rocksdb to v9.11.2 is clear and concise. Please verify that the date formatting (e.g. "Apr 9, 2025") and heading style align with the project’s changelog conventions.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

9-9: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)


15-16: v1.4.6 Bug Fixes – Edge Case and Ethermint Updates

The bug fixes for eth_getLogs (line 15) and the inclusion of ethermint bug fixes (line 16) are well-documented with proper PR references. However, the URL in the parentheses for [#1785] is a bare URL. To improve consistency and adhere to markdown best practices, consider formatting it as a proper markdown link.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

16-16: Bare URL used
null

(MD034, no-bare-urls)


28-29: v1.4.5 Bug Fixes – Version Mismatch and Security Patch

The fixes addressing the version mismatch and the inclusion of the ibc-go security patch are explained well. Consider rephrasing “Fix version mismatch happen occasionally” to “Fix occasional version mismatch” for better grammatical clarity.


46-47: v1.4.4 Improvements – Batch Initialization and Flush Behavior

The improvement entry for skipping batch initialization and flush when using a dry-run (line 46) is clear. For clarity, consider rephrasing “avoid run fixdata multiple times” (as mentioned in the related bug fix entry) to “avoid multiple executions of fixdata.”

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

47-47: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7e92086 and 60e0d27.

⛔ Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
📒 Files selected for processing (3)
  • CHANGELOG.md (1 hunks)
  • go.mod (1 hunks)
  • gomod2nix.toml (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • go.mod
  • gomod2nix.toml
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
CHANGELOG.md

9-9: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)


16-16: Bare URL used
null

(MD034, no-bare-urls)


22-22: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)


31-31: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)


47-47: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)


55-55: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

⏰ Context from checks skipped due to timeout of 90000ms (16)
  • GitHub Check: integration_tests (gas)
  • GitHub Check: integration_tests (slow)
  • GitHub Check: integration_tests (upgrade)
  • GitHub Check: integration_tests (gov)
  • GitHub Check: integration_tests (ica)
  • GitHub Check: integration_tests (ibc_update_client)
  • GitHub Check: integration_tests (ibc_timeout)
  • GitHub Check: integration_tests (ibc_rly_gas)
  • GitHub Check: build (macos-14)
  • GitHub Check: integration_tests (ibc_rly_evm)
  • GitHub Check: unittest
  • GitHub Check: integration_tests (ibc)
  • GitHub Check: build (macos-latest)
  • GitHub Check: integration_tests (unmarked)
  • GitHub Check: build (ubuntu-latest)
  • GitHub Check: Run golangci-lint
🔇 Additional comments (2)
CHANGELOG.md (2)

20-22: v1.4.6 Improvements – memiavl LoadVersion Behavior

The entry stating that "memiavl LoadVersion loads up to the target version instead of exact version" is succinct and clear. Ensure that any related documentation or upstream references reflect this change accurately.

🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

22-22: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)


40-42: v1.4.4 Bug Fixes – Legacy AccountNumber Support and Security Patch

In the v1.4.4 section, the bug fixes include:

  • Support for legacy global AccountNumber (line 40)
  • A security patch from ibc-go (line 42)

Please verify that the ordering and grouping of these entries are intentional and that any duplicate mentions (if similar fixes appear in other versions) are deliberate. Consistency in the description across versions is important.

@mmsqe mmsqe added this pull request to the merge queue Apr 11, 2025
Merged via the queue into crypto-org-chain:main with commit 18ac7f4 Apr 11, 2025
37 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Sep 3, 2025
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.

3 participants