Skip to content

Conversation

@thomas-nguy
Copy link
Collaborator

@thomas-nguy thomas-nguy commented Aug 22, 2025

👮🏻👮🏻👮🏻 !!!! 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

  • Documentation
    • Updated Unreleased changelog with a bug fix entry for “version not found during pruning” and added a dated marker ahead of the next release.
  • Chores
    • Pinned a core dependency to a stable version to ensure consistent builds and reproducibility.
    • Updated associated build metadata to reflect the dependency change.

@thomas-nguy thomas-nguy requested a review from a team as a code owner August 22, 2025 05:31
@thomas-nguy thomas-nguy requested review from JayT106 and randy-cro and removed request for a team August 22, 2025 05:31
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 22, 2025

Walkthrough

Pins github.com/cosmos/iavl to v1.2.6 in go.mod and gomod2nix.toml (including updated hash and replace metadata) and adds an UNRELEASED CHANGELOG entry noting a pruning-related bug fix reference.

Changes

Cohort / File(s) Summary
Documentation
CHANGELOG.md
Added UNRELEASED section with Bug fixes bullet for PR #1858 and date “Jun 20, 2025” before v1.4.8 entry.
Go module pinning
go.mod
Added replace directive to pin github.com/cosmos/iavl to v1.2.6.
Nix module map update
gomod2nix.toml
Updated github.com/cosmos/iavl version to v1.2.6, refreshed SHA256, and added replaced = "github.com/cosmos/iavl" field.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested labels

backport/v1.4.x

Suggested reviewers

  • leejw51crypto
  • mmsqe
  • yihuang

Poem

A nibble of notes in CHANGELOG land,
A hop to v1.2.6, dependencies planned.
Pruning paths trimmed, tidy and neat,
Hashes refreshed—oh what a treat!
With whiskers twitching, I stamp and sign:
“Pinned and pruned—now everything’s fine.” 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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: 1

🧹 Nitpick comments (2)
go.mod (1)

302-304: Add a small regression test exercising pruning around a missing version.

This change fixes a production bug-path; please add a test that reproduces the “version does not exist” scenario and passes with v1.2.6 to prevent regressions.

I can sketch a minimal test that populates a tree with versions, prunes a range including a recent version, and asserts subsequent LoadVersion/Commit behavior succeeds. Want me to open a follow-up PR with that?

CHANGELOG.md (1)

22-25: Make the entry explicit about the dependency pin and symptom.

Consider clarifying that the fix is delivered by pinning iavl to v1.2.6, and echo the user-facing symptom to help operators scanning the log.

Apply this diff to improve the bullet:

- * [#1858](https://github.com/crypto-org-chain/cronos/pull/1858) Fix version not found during pruning.
+ * [#1858](https://github.com/crypto-org-chain/cronos/pull/1858) deps(iavl): pin to v1.2.6 to fix pruning error “version does not exist”.
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 1f80cb2 and a66d4b1.

⛔ 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 (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (17)
  • GitHub Check: build (macos-latest)
  • GitHub Check: build (macos-14)
  • GitHub Check: build (ubuntu-latest)
  • GitHub Check: unittest
  • GitHub Check: gomod2nix
  • GitHub Check: integration_tests (slow)
  • GitHub Check: integration_tests (gas)
  • GitHub Check: integration_tests (gov)
  • GitHub Check: integration_tests (ibc)
  • GitHub Check: integration_tests (ibc_rly_gas)
  • GitHub Check: integration_tests (upgrade)
  • GitHub Check: integration_tests (ibc_update_client)
  • GitHub Check: integration_tests (ica)
  • GitHub Check: integration_tests (ibc_timeout)
  • GitHub Check: integration_tests (ibc_rly_evm)
  • GitHub Check: integration_tests (unmarked)
  • GitHub Check: Run golangci-lint
🔇 Additional comments (3)
go.mod (1)

302-304: LGTM: Pinning iavl to v1.2.6 to address pruning “version does not exist”.

The targeted replace is scoped and low risk; good call pinning to a known-good upstream for this bug.

gomod2nix.toml (2)

232-234: LGTM: gomod2nix pinned to iavl v1.2.6 with updated checksum and replaced marker.

The Nix metadata mirrors go.mod; this keeps CI/builds reproducible across environments.


232-234: Confirm gomod2nix iavl hash correctness

Please ensure the sha256 value for the github.com/cosmos/iavl module matches the output of the gomod2nix generate tool. If this stanza was edited by hand (rather than produced by the generator), rerun the tool to prevent checksum drift.

Locations to verify:

  • gomod2nix.toml, lines 231–234

Current block:

[mod."github.com/cosmos/iavl"]
  version  = "v1.2.6"
  hash     = "sha256-9kLtVepU5b3m2Sne8pBQNvF9LxM374LEmvuLWeYBfFU="
  replaced = "github.com/cosmos/iavl"

If these values weren’t generated by running:

nix develop -c gomod2nix generate   # or: nix run .#gomod2nix -- generate

please do so and commit the updated hash output.

@codecov
Copy link

codecov bot commented Aug 22, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 35.81%. Comparing base (a3c2f70) to head (a66d4b1).
⚠️ Report is 101 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##             main    #1858       +/-   ##
===========================================
+ Coverage   16.87%   35.81%   +18.94%     
===========================================
  Files          72      127       +55     
  Lines        6163    11812     +5649     
===========================================
+ Hits         1040     4231     +3191     
- Misses       5000     7158     +2158     
- Partials      123      423      +300     

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

Copy link
Contributor

@JayT106 JayT106 left a comment

Choose a reason for hiding this comment

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

LGTM

@thomas-nguy thomas-nguy added this pull request to the merge queue Aug 29, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Aug 29, 2025
@thomas-nguy thomas-nguy added this pull request to the merge queue Aug 29, 2025
Merged via the queue into crypto-org-chain:main with commit e6745e4 Aug 29, 2025
42 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