test(katana-executor): katana to blockifier chain id invariant

[kariy]

add invariant test for issue on chain id

Closes #1595.

Summary by CodeRabbit

• Bug Fixes

  • Improved handling of chain IDs in test functions for clarity and efficiency.

• New Features

  • Added a new test function to ensure consistency of chain ID during syscalls in the blockifier.

[coderabbitai]

Walkthrough

Ohayo, sensei! This update refines the test functions in the utils.rs file by simplifying chain ID handling, transitioning from direct enum conversions to using constants for improved clarity. It also introduces a new test, blockifier_chain_id_invariant, ensuring chain ID consistency during syscalls, thereby enhancing the overall structure and clarity of the tests.

Changes

File Path	Change Summary
crates/katana/executor/src/implementation/blockifier/utils.rs	Simplified chain ID handling in tests using constants instead of enums; added a new syscall consistency test.

Sequence Diagram(s)

sequenceDiagram
    participant Test
    participant Blockifier
    participant ChainId

    Test->>Blockifier: Call with chain ID
    Blockifier->>ChainId: Retrieve corresponding chain ID
    ChainId-->>Blockifier: Return MAINNET or SEPOLIA
    Blockifier-->>Test: Validate chain ID consistency

Loading

This diagram illustrates the interaction between the test, blockifier, and chain ID retrieval process.

---

Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6d14739 and 1ca619d.

Files selected for processing (1)

• crates/katana/executor/src/implementation/blockifier/utils.rs (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• crates/katana/executor/src/implementation/blockifier/utils.rs

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.20%. Comparing base (25da1a8) to head (1ca619d).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2204      +/-   ##
==========================================
+ Coverage   68.18%   68.20%   +0.01%     
==========================================
  Files         336      336              
  Lines       44038    44056      +18     
==========================================
+ Hits        30029    30048      +19     
+ Misses      14009    14008       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.