chore(verifier): bump dependencies

[rimrakhimov]

• Bump alloy dependencies to v0.8.20
• Bump verification-common to rev 8d9cf0e

Summary by CodeRabbit

• Chores

  • Updated core dependencies to their latest versions, ensuring improved reliability and compatibility.

• Refactor

  • Enhanced the process for handling contract ABI data during constructor argument processing, leading to more consistent and robust behavior.
  • Improved the logic for determining match types in contract verification, shifting from type-based to metadata-based criteria.
  • Updated logging for contract verification results to provide clearer and more structured output regarding match types.

[coderabbitai]

Warning

Rate limit exceeded

@rimrakhimov has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 9 minutes and 35 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between d5a89de and 4c11157.

⛔ Files ignored due to path filters (1)

• smart-contract-verifier/Cargo.lock is excluded by !**/*.lock

📒 Files selected for processing (6)

• smart-contract-verifier/Cargo.toml (2 hunks)
• smart-contract-verifier/smart-contract-verifier-server/src/services/zksync_solidity_verifier.rs (1 hunks)
• smart-contract-verifier/smart-contract-verifier-server/tests/test_cases_zksync_solidity/era_solidity_0.8.28.json (1 hunks)
• smart-contract-verifier/smart-contract-verifier-server/tests/test_cases_zksync_solidity/simple_standard_json.json (1 hunks)
• smart-contract-verifier/smart-contract-verifier-server/tests/test_cases_zksync_solidity/zksolc_1_3_5.json (1 hunks)
• smart-contract-verifier/smart-contract-verifier/src/zksync/implementation.rs (1 hunks)

Walkthrough

The pull request updates dependency versions and modifies ABI parsing in the smart-contract-verifier project. The versions for both alloy-dyn-abi and alloy-json-abi are updated from 0.6.4 to 0.8.20 in the Cargo.toml file. Additionally, code within the process_constructor_arguments function in the transformations module is altered to switch from using from_json_str to deserialize for ABI deserialization. The logic for handling invalid constructor arguments remains unchanged. Furthermore, the process_match function's logic is modified to determine the match type based on metadata rather than type. Lastly, logging in the verify_compiler_output function is enhanced to provide clearer match type representations. These changes are isolated to dependency version bumps and adjustments to ABI parsing and logging, with no other functional modifications.

Possibly related PRs

• fix(eth-bytecode-db): bump verification-common to support non-map 'compilation_artifacts.sources' values #1216: The changes in the main PR are related to the updates made to the verification-common dependency, which is also modified in the retrieved PR, indicating a direct connection at the code level.
• chore(verifier): extract dependencies into workspace #1232: The changes in the main PR, which update dependency versions in Cargo.toml, are related to the retrieved PR that also modifies the Cargo.toml file by adding and restructuring dependencies, including alloy-dyn-abi and alloy-json-abi.

Poem

I'm a little rabbit, hopping with glee,
Upgrading dependencies as sprightly as can be.
From version old to new, my code now sings,
Deserializing ABIs with magical wings.
ASCII carrots and 🥕 dreams, I leap,
Celebrating clean code in every hop I keep!

---

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.