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: app hash mismatch in block-stm #1539

Merged
merged 8 commits into from
Aug 6, 2024

Conversation

yihuang
Copy link
Collaborator

@yihuang yihuang commented Aug 5, 2024

Solution:

  • try to reproduce in integration test first

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

  • New Features

    • Introduced new configuration settings for memiavl with options for enabling, zero-copy, and snapshot intervals.
    • Increased the number of block-stm-workers for enhanced performance.
  • Bug Fixes

    • Added documentation about a resolved bug related to application hash mismatch in the go-block-stm.
  • Chores

    • Updated module dependencies to improve overall stability and performance.

Solution:
- try to reproduce in integration test first
Copy link
Contributor

coderabbitai bot commented Aug 5, 2024

Walkthrough

The recent changes enhance a Go project's configuration and dependency management. The go.mod file sees a reclassification of dependencies, while gomod2nix.toml updates version information for better compatibility. Integration tests gain new functionalities, and configuration settings are optimized to improve blockchain transaction performance and concurrency.

Changes

Files Change Summary
go.mod, gomod2nix.toml Removed github.com/cosmos/cosmos-proto from require, added as indirect; updated go-block-stm version and hash.
integration_tests/configs/default.jsonnet Increased block-stm-workers from 16 to 32, enhancing concurrency for improved performance.
integration_tests/test_basic.py Added functions for account derivation, transaction signing, and block waiting; introduced test_block_stm_delete.
CHANGELOG.md Added entry for bug fix in go-block-stm related to application hash mismatch.

Poem

In fields of code, we leap with glee,
Dependencies shift like leaves on a tree.
With block-stm strong and memiavl bright,
Testing our magic, we soar to new heights!
Hopping through changes, we joyfully play,
A rabbit’s delight in the code today! 🐇✨


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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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 Aug 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.12%. Comparing base (cb8366b) to head (52b4fe5).

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##             main    #1539       +/-   ##
===========================================
+ Coverage   15.24%   36.12%   +20.88%     
===========================================
  Files          67       97       +30     
  Lines        4874     7725     +2851     
===========================================
+ Hits          743     2791     +2048     
- Misses       4037     4585      +548     
- Partials       94      349      +255     

see 47 files with indirect coverage changes

yihuang and others added 5 commits August 5, 2024 15:44
Co-authored-by: mmsqe <mavis@crypto.com>
Signed-off-by: yihuang <huang@crypto.com>
@yihuang yihuang marked this pull request as ready for review August 6, 2024 08:06
@yihuang yihuang requested a review from a team as a code owner August 6, 2024 08:06
@yihuang yihuang requested review from calvinaco, thomas-nguy and mmsqe and removed request for a team August 6, 2024 08:06
@yihuang yihuang enabled auto-merge August 6, 2024 08:06
Copy link
Collaborator

@mmsqe mmsqe left a comment

Choose a reason for hiding this comment

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

might need a change log?

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

Outside diff range, codebase verification and nitpick comments (1)
integration_tests/test_basic.py (1)

942-976: LGTM!

The new test case test_block_stm_delete effectively validates the functionality of block-stm by addressing a specific bug.

Suggestion: Add a timeout to the w3_wait_for_block function call.

- w3_wait_for_block(w3, w3.eth.block_number + 3, timeout=30)
+ w3_wait_for_block(w3, w3.eth.block_number + 3, timeout=30)
Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between cb8366b and a7f2b12.

Files ignored due to path filters (1)
  • go.sum is excluded by !**/*.sum
Files selected for processing (4)
  • go.mod (3 hunks)
  • gomod2nix.toml (1 hunks)
  • integration_tests/configs/default.jsonnet (2 hunks)
  • integration_tests/test_basic.py (2 hunks)
Additional comments not posted (8)
integration_tests/configs/default.jsonnet (2)

26-30: LGTM!

The addition of the memiavl configuration block with parameters enable, zero-copy, and snapshot-interval enhances memory management capabilities.


51-51: LGTM!

The modification of the block-stm-workers parameter from 16 to 32 improves concurrency for block processing.

go.mod (3)

90-90: LGTM!

The removal of github.com/cosmos/cosmos-proto v1.0.0-beta.5 from the main require block indicates that the project no longer directly relies on this version of the cosmos-proto library.


90-90: LGTM!

The reintroduction of github.com/cosmos/cosmos-proto v1.0.0-beta.5 as an indirect dependency ensures compatibility or functionality through transitive dependencies.


100-100: LGTM!

The version update for github.com/crypto-org-chain/go-block-stm from v0.0.0-20240408011717-9f11af197bde to v0.0.0-20240806075927-09a64748f883 may include bug fixes, new features, or other improvements.

integration_tests/test_basic.py (1)

28-37: LGTM!

The addition of new functions derive_new_account, sign_transaction, and w3_wait_for_block expands the capabilities of the test cases, enhancing the testing framework.

gomod2nix.toml (2)

217-217: Verify the correctness of the hash update.

The hash for github.com/crypto-org-chain/go-block-stm has been updated to sha256-DuqcnTqpUVRxV+I+CaBuDg/1CLmMeXdw4VEFeuCsUbU=. Ensure that this new hash is correct and matches the module's integrity.


216-216: Verify the compatibility and stability of the version update.

The version for github.com/crypto-org-chain/go-block-stm has been updated to v0.0.0-20240806075927-09a64748f883. Ensure that this new version is compatible and stable with the rest of the codebase.

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a7f2b12 and a6d0d7f.

Files selected for processing (1)
  • integration_tests/configs/default.jsonnet (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • integration_tests/configs/default.jsonnet

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a6d0d7f and 52b4fe5.

Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
Files skipped from review due to trivial changes (1)
  • CHANGELOG.md

@yihuang yihuang added this pull request to the merge queue Aug 6, 2024
Merged via the queue into crypto-org-chain:main with commit bb51671 Aug 6, 2024
33 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