Problem: fix of state overwrite in debug trace is not included

[mmsqe]

👮🏻👮🏻👮🏻 !!!! 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 validator benchmark execution.
  • Fixed node shutdown issues via signal.
  • Eliminated conflicts in benchmark transactions.
  • Addressed state overwrite in debug trace APIs.

• Improvements

  • Enabled parallel generation of test transactions on a single node.
  • Introduced a retry mechanism for load generators.
  • Added abort options in the PrepareProposal function.
  • Implemented batch mode support for benchmarks.

• Chores

  • Updated module dependencies and versions for improved compatibility and security.

[coderabbitai[bot]]

Walkthrough

The pull request includes updates to the CHANGELOG.md, go.mod, and gomod2nix.toml files for the cronos project. The changelog highlights several bug fixes and improvements, while the go.mod and gomod2nix.toml files reflect significant updates to module dependencies, including version changes and replacements for certain modules. These changes ensure compatibility with newer versions and address potential vulnerabilities.

Changes

File	Change Summary
CHANGELOG.md	- Added bug fixes: running a single validator benchmark, node shutdown via signal, state overwrite in debug trace APIs. - Added improvements: parallel test transaction generation, load generator retry with backoff, abort options in PrepareProposal, benchmark batch mode support.
go.mod	- Updated Go version from 1.22.2 to 1.22.3. - Updated dependency: github.com/evmos/ethermint to new version. - Replaced dependencies: github.com/99designs/keyring with github.com/cosmos/keyring, github.com/dgrijalva/jwt-go with github.com/golang-jwt/jwt/v4, and others.
gomod2nix.toml	- Updated versions and hashes for github.com/evmos/ethermint, github.com/ethereum/go-ethereum, and github.com/cosmos/cosmos-sdk. - Marked github.com/ethereum/go-ethereum as replaced with github.com/crypto-org-chain/go-ethereum.

Possibly related PRs

• #1568: Updates CHANGELOG.md to include a note about the update of the cometbft library.
• #1569: Adds an entry in CHANGELOG.md regarding a crash issue fix in the Ethermint project.
• #1578: Updates CHANGELOG.md to reflect the release of version 1.4.0-rc0.
• #1647: Addresses the issue where the node could not shut down via signal.
• #1648: Introduces a feature to allow aborting operations in the PrepareProposal function.
• #1649: Documents a fix for running a single validator benchmark locally.

Suggested reviewers

• calvinaco
• yihuang

🐰 In the land of code, where changes abound,
A changelog updated, with fixes profound.
Dependencies shifted, like leaves in the breeze,
With each little change, our project finds ease.
So hop with delight, let our progress be known,
For every small fix, our garden has grown! 🌱

---

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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

🪧 Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 34.94%. Comparing base (ad53734) to head (5d924fb). Report is 1 commits behind head on main.

Additional details and impacted files

[](https://app.codecov.io/gh/crypto-org-chain/cronos/pull/1655?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=crypto-org-chain) ```diff @@ Coverage Diff @@ ## main #1655 +/- ## =========================================== + Coverage 16.64% 34.94% +18.29% =========================================== Files 72 123 +51 Lines 6212 11803 +5591 =========================================== + Hits 1034 4124 +3090 - Misses 5055 7265 +2210 - Partials 123 414 +291 ``` [see 69 files with indirect coverage changes](https://app.codecov.io/gh/crypto-org-chain/cronos/pull/1655/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=crypto-org-chain)