-
Notifications
You must be signed in to change notification settings - Fork 116
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
fix: skip block scanning actions on Arbitrum and Avalanch networks (v27) #3554
fix: skip block scanning actions on Arbitrum and Avalanch networks (v27) #3554
Conversation
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (1)
Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
Documentation and Community
|
|
||
// Initialize lastScannedTssRecvd to a known "unset" value | ||
var lastScannedTssRecvd uint64 = 0 // Assuming 0 is an appropriate "unset" value | ||
if ob.Chain().ChainId != 421614 && ob.Chain().ChainId != 42161 && ob.Chain().ChainId != 43113 && ob.Chain().ChainId != 43114 { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@morde08 There has to be a better way to write line 152, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reverse the check with Ethereum chain IDs
chainID := ob.Chain().ChainId
if chainID == 1 || chainID == 11155111 || chainID == 1337
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will be a far larger check once we pull in BSC and Polygon where direct TSS deposits are still supported presumably, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's define a slice containing all chain ids and use https://pkg.go.dev/slices#Contains
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release/v27 #3554 +/- ##
===============================================
- Coverage 64.42% 64.30% -0.12%
===============================================
Files 436 436
Lines 30380 30435 +55
===============================================
Hits 19571 19571
- Misses 9968 10023 +55
Partials 841 841
|
Description
This PR takes a hatchet to zetaclient/chains/evm/observer/inbound.go to validate the expected gains from not observing TSS direct transfers on Arbitrum and Avalanche.
How Has This Been Tested?