zeta-chain / protocol-contracts

Protocol contracts implementing the core logic of the protocol, deployed on ZetaChain and on connected chains
MIT License
71 stars 58 forks source link

fix: address warnings in build #399

Closed lumtis closed 1 month ago

lumtis commented 1 month ago

Mainly comment out unused parameter or variables

NOTE: the test failure should be fixed once https://github.com/zeta-chain/protocol-contracts/pull/393 is merged

Summary by CodeRabbit

Release Notes

coderabbitai[bot] commented 1 month ago
πŸ“ Walkthrough
πŸ“ Walkthrough ## Walkthrough This pull request includes modifications to several contracts and test files within the ZetaChain protocol. Key changes involve the removal of the `internalSendHash` parameter from the `withdraw`, `withdrawAndCall`, and `withdrawAndRevert` functions in the `ZetaConnectorNative` contract. Additionally, new test functions and event updates are introduced across various test contracts to enhance coverage and ensure proper functionality, particularly in relation to withdrawal operations. The overall structure and logic of the contracts remain unchanged despite these adjustments. ## Changes | File Path | Change Summary | |---------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| | v2/contracts/evm/ZetaConnectorNative.sol | Updated method signatures for `withdraw`, `withdrawAndCall`, and `withdrawAndRevert` to comment out `internalSendHash`. | | v2/test/ERC20Custody.t.sol | Added `testUpgradeAndWithdraw` method to test upgrade process and withdrawal functionality; enhanced role management checks; refined existing tests. | | v2/test/GatewayZEVM.t.sol | Added `WithdrawnV2` event; updated `testWithdrawZRC20` and related functions to include new event and additional failure checks. | | v2/test/ZRC20.t.sol | Added checks for gas fee withdrawal; ensured comprehensive coverage of `ZRC20` functionalities and constraints. | | v2/test/fuzz/ERC20CustodyEchidnaTest.sol | Introduced `ERC20CustodyEchidnaTest` contract; added `testWithdrawAndCall` method to test withdrawal functionality. | | v2/test/fuzz/GatewayEVMEchidnaTest.sol | Introduced `GatewayEVMEchidnaTest` contract; added `testExecuteWithERC20` method to test ERC20 token execution. | | v2/test/utils/ReceiverEVM.sol | Updated `onCall` function to remove parameter names; added return statement. | | v2/test/utils/SenderZEVM.sol | Added `CallOptions` structure; updated `callReceiver` and `withdrawAndCallReceiver` functions to use `CallOptions`. | | v2/test/utils/TestUniversalContract.sol | Updated `onCall` function to comment out parameter names while retaining their types. | | v2/test/utils/upgrades/ZetaConnectorNativeUpgradeTest.sol | Renamed `Withdrawn` event to `WithdrawnV2`; updated withdrawal function signatures to comment out `internalSendHash`. | ## Possibly related issues - **zeta-chain/protocol-contracts#307**: This PR addresses the objective of adding `CallOptions` containing a gas limit for `call` and `withdrawAndCall` functions, which relates to the changes in the `SenderZEVM` contract. ## Possibly related PRs - **#178**: The changes in the `GatewayEVM` and `ERC20Custody` contracts regarding the handling of various functions and roles are related to the modifications in the `ZetaConnectorNative` contract, particularly in the context of managing withdrawal functionalities and role assignments. - **#361**: The addition of the `sender` field in the `RevertContext` struct enhances the context during revert operations, which aligns with the changes in the `GatewayEVM` contract that also focus on improving error handling and context management. - **#370**: The introduction of checks to prevent zero gas limits in the `GatewayEVM` contract is directly related to the changes in the main PR, which also involve modifications to the `withdrawAndCall` and `call` functions. - **#376**: The enforcement of payload size limits in the `GatewayEVM` contract is relevant to the main PR's focus on improving the robustness of contract interactions, particularly in the context of withdrawal and call functions. - **#385**: The transition of the `ERC20Custody` and `ZetaConnector` contracts to upgradeable contracts is related to the main PR's focus on enhancing the functionality and management of these contracts, particularly in the context of role assignments and initialization. - **#386**: The addition of the `PAUSER_ROLE` to the TSS address in the `ERC20Custody` and `GatewayEVM` contracts is relevant to the main PR's focus on role management and enhancing control mechanisms within the contracts. - **#393**: The refactoring to disable ZETA-related functions and the removal of outdated methods aligns with the main PR's focus on streamlining the codebase and improving the overall functionality of the contracts. ## Suggested reviewers - fadeev - CharlieMc0 - andresaiello - brewmaster012 - fbac

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. ### 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-commenter commented 1 month ago

Codecov Report

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

Project coverage is 84.23%. Comparing base (db2f95f) to head (271267b).

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #399 +/- ## ======================================= Coverage 84.23% 84.23% ======================================= Files 8 8 Lines 387 387 Branches 121 121 ======================================= Hits 326 326 Misses 61 61 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.