fix: fix query txs error

[wangjiulian]

Summary by CodeRabbit

• Chores
  • Updated multiple project dependencies to their latest compatible versions
  • Upgraded versions for libraries including CometBFT, Prometheus, Go-kit, and others
  • Ensured dependency versions are current and compatible with the project requirements

[coderabbitai]

Walkthrough

This pull request focuses on updating multiple Go module dependencies to their latest compatible versions. The changes involve incrementing version numbers for various libraries used in the project, including CometBFT, Prometheus client libraries, deadlock detection, database utilities, and OAuth2 packages. These updates aim to incorporate the most recent patches, potential bug fixes, and improvements from the respective library maintainers.

Changes

File	Change Summary
go.mod	Updated 11 dependencies, including: - CometBFT: v0.38.12 → v0.38.15 - Prometheus client_golang: v1.20.1 → v1.20.5 - OAuth2: v0.22.0 → v0.23.0

Possibly related PRs

• Update dependencies #2985: Previous OAuth2 dependency update from v0.21.0 to v0.22.0

Poem

🐰 Hop, hop, dependencies dance!
Versions climbing with each new chance
Go modules update, libraries grow
Patches and fixes in a rhythmic flow
Coding rabbit's dependency delight! 🚀

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between b2a0de8 and ccbc8d1.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (1)

• go.mod (5 hunks)

🔇 Additional comments (4)

go.mod (4)

252-252: Verify the stability of bbolt alpha version.

The update to go.etcd.io/bbolt v1.4.0-alpha.0.20240404170359-43604f3112c5 introduces an alpha version. Alpha releases may contain breaking changes or unstable features.

Let's check for any known issues or breaking changes:

✅ Verification successful

The alpha version appears stable and well-tested.

The update to bbolt v1.4.0-alpha includes several important improvements:

• Enhanced data safety through key copying in operations
• New features like MoveBucket and Inspect
• Improved diagnostics and CLI tools
• Extensive robustness testing including power failure scenarios

While this is an alpha version, the changes are focused on improvements rather than breaking changes, and the codebase shows thorough testing coverage.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for any references to bbolt in the codebase and potential breaking changes
echo "Checking bbolt usage..."
rg --type go "bbolt" -B 2 -A 2

# Check commit messages between the versions for breaking changes
echo "Checking version changes..."
gh api repos/etcd-io/bbolt/compare/v1.3.10...43604f3112c5 --jq '.commits[].commit.message'

Length of output: 40702

---

256-256: Consider updating oauth2 to the latest version.

The oauth2 package is updated to v0.23.0, but newer versions are available. Consider updating to the latest stable version for security improvements.

Let's check the oauth2 usage and available versions:

---

8-8: Verify compatibility with updated dependencies.

Several dependencies have been updated to newer versions:

• CometBFT: v0.38.12 -> v0.38.15
• Prometheus client: v1.20.1 -> v1.20.5
• Prometheus common: v0.55.0 -> v0.60.1
• go-deadlock: v0.3.1 -> v0.3.5

These updates appear to be minor version bumps focusing on bug fixes and improvements.

Let's verify if these updates align with the PR objective of fixing transaction query errors:

Also applies to: 227-227, 229-229, 236-236

✅ Verification successful

Dependency updates appear safe to proceed

The updates are primarily patch version increments focusing on bug fixes and improvements:

• CometBFT (0.38.12 -> 0.38.15): Patch version update maintaining compatibility
• Prometheus client/common: Metrics-only changes, not affecting core transaction functionality
• go-deadlock: Development tool update, no production impact

These changes align with the PR objective of fixing transaction query errors, as patch version updates typically include bug fixes while maintaining backward compatibility.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for any transaction-related code that might be affected by CometBFT update
echo "Checking transaction-related code..."
rg --type go "func.*Tx.*Query" -B 2 -A 2

# Check for any prometheus metrics related to transactions
echo "Checking transaction metrics..."
rg --type go 'NewCounter.*Tx|NewHistogram.*Tx|NewGauge.*Tx' -B 2 -A 2

Length of output: 270

---

Script:

#!/bin/bash
# Check for CometBFT imports and usage
echo "Checking CometBFT imports..."
rg --type go "github.com/cometbft/cometbft" -B 1 -A 1

# Check for transaction-related code with broader patterns
echo "Checking transaction-related code..."
rg --type go "(type|func).*[Tt]x.*|[Tt]ransaction" -B 2 -A 2

# Check for any configuration or initialization code
echo "Checking configuration and init code..."
rg --type go "(New|Init|Config).*Client" -B 2 -A 2

# Look for any changelog references
echo "Checking for changelog references..."
fd "CHANGELOG" --type f --exec cat {}

Length of output: 67373

---

Script:

#!/bin/bash
# Check for any CometBFT changelog entries in the repository
echo "Checking for CometBFT changelog references..."
fd -t f -e md CHANGELOG -e txt | xargs rg -i "comet.*0\.38\.(13|14|15)|transaction.*fix"

# Look for any transaction error handling code
echo "Checking transaction error handling..."
rg --type go "func.*HandleTx|func.*ProcessTx|func.*ValidateTx" -B 2 -A 2

# Check for any CometBFT configuration
echo "Checking CometBFT configuration..."
rg --type go "CometConfig|cometbft.*Config" -B 2 -A 2

Length of output: 488

---

Line range hint 271-282: Review replace directives for potential conflicts.

The replace directives show:

1. Using a fork of ethermint
2. Pinning goleveldb to a specific version
3. Pinning hid to v0.9.0
4. Pinning golang.org/x/exp to a specific commit

These pinned versions might affect the stability of the updated dependencies.

Let's check for any potential conflicts:

✅ Verification successful

Replace directives are valid and well-documented

The replace directives are intentionally pinned with clear rationale:

• Ethermint fork is a standard practice for blockchain customization
• Other pins are defensive measures with documented reasons to maintain stability
• All versions are consistent between go.mod and go.sum

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if any of the replaced packages are required by the updated dependencies
echo "Checking dependency tree..."
go mod graph | grep -E "github.com/syndtr/goleveldb|github.com/zondax/hid|golang.org/x/exp"

Length of output: 251

---

Script:

#!/bin/bash
# Check for direct imports of replaced packages
echo "Checking direct imports..."
ast-grep --pattern 'import (
  $$$
  "$_goleveldb"
  $$$
)' | grep -E "github.com/syndtr/goleveldb"

ast-grep --pattern 'import (
  $$$
  "$_hid"
  $$$
)' | grep -E "github.com/zondax/hid"

ast-grep --pattern 'import (
  $$$
  "$_exp"
  $$$
)' | grep -E "golang.org/x/exp"

ast-grep --pattern 'import (
  $$$
  "$_ethermint"
  $$$
)' | grep -E "github.com/evmos/ethermint"

echo -e "\nChecking go.sum for version information..."
cat go.sum | grep -E "github.com/syndtr/goleveldb|github.com/zondax/hid|golang.org/x/exp|github.com/evmos/ethermint"

Length of output: 1253

---

Script:

#!/bin/bash
echo "Checking go.mod for version constraints..."
cat go.mod | grep -A 5 -B 5 "require" 

Length of output: 1976

---

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
• Mastodon
• Reddit
• LinkedIn

🪧 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. (Beta)
• @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.