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: integration test don't verify app hash between block-stm and #1538

Merged
merged 5 commits into from
Aug 5, 2024

Conversation

yihuang
Copy link
Collaborator

@yihuang yihuang commented Aug 5, 2024

sequential

Solution:

  • only enable block-stm on one of the node, try to detect potencial app hash mismatch

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

    • Improved organization of configuration settings for better clarity and management, particularly for Ethereum Virtual Machine (EVM) parameters.
  • Bug Fixes

    • Streamlined configuration structure may reduce potential confusion and errors related to mempool and versiondb settings.

sequential

Solution:
- only enable block-stm on one of the node, try to detect potencial app
  hash mismatch
@yihuang yihuang requested a review from a team as a code owner August 5, 2024 04:20
@yihuang yihuang requested review from JayT106 and leejw51crypto and removed request for a team August 5, 2024 04:20
Copy link
Contributor

coderabbitai bot commented Aug 5, 2024

Walkthrough

The recent changes reorganize the configuration settings in default.jsonnet, specifically with respect to the Ethereum Virtual Machine (EVM). The evm block has been removed from the mempool settings and reintroduced under the versiondb section for validators. This restructuring consolidates related settings, enhances clarity, and introduces new parameters, all while maintaining overall functionality.

Changes

Files Change Summary
integration_tests/configs/default.jsonnet Removed evm block from mempool; reintroduced under versiondb for validators with additional settings for improved clarity and differentiation.

Sequence Diagram(s)

(No sequence diagrams generated as the changes do not involve new features or modifications to control flow.)

Poem

🐰 In the config garden, changes bloom,
The evm now finds a new room.
From mempool it took flight,
To versiondb shines bright!
A clearer path for all to see,
Hop along, joyfully! 🌼✨


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.

@yihuang yihuang requested a review from mmsqe August 5, 2024 04:24
Signed-off-by: yihuang <huang@crypto.com>
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 b4bec82 and ec6b021.

Files selected for processing (1)
  • integration_tests/configs/default.jsonnet (2 hunks)
Additional comments not posted (2)
integration_tests/configs/default.jsonnet (2)

29-29: Verify the impact of removing the evm block from the mempool section.

Ensure that removing the evm block from the mempool section does not affect any dependent functionality or configurations.


47-49: Ensure correct integration of the evm block in the versiondb section.

Verify that the evm block is correctly integrated within the versiondb section for validators and that it does not cause any issues with the existing configuration.

@yihuang yihuang enabled auto-merge August 5, 2024 04:27
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 ec6b021 and b63a15f.

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

Copy link

codecov bot commented Aug 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 15.24%. Comparing base (b4bec82) to head (4ba9d61).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #1538   +/-   ##
=======================================
  Coverage   15.24%   15.24%           
=======================================
  Files          67       67           
  Lines        4874     4874           
=======================================
  Hits          743      743           
  Misses       4037     4037           
  Partials       94       94           

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 b63a15f and 2bd7bf0.

Files selected for processing (1)
  • integration_tests/configs/default.jsonnet (3 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 2bd7bf0 and 4ba9d61.

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

@yihuang yihuang added this pull request to the merge queue Aug 5, 2024
Merged via the queue into crypto-org-chain:main with commit cb8366b Aug 5, 2024
34 checks passed
@yihuang yihuang deleted the reproduce-stm-apphash branch August 5, 2024 07:32
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