-
Notifications
You must be signed in to change notification settings - Fork 108
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: don't skip unsupported chain param and let it update the IsSupported
flag in context
#2233
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #2233 +/- ##
========================================
Coverage 68.06% 68.06%
========================================
Files 259 259
Lines 16017 16014 -3
========================================
- Hits 10902 10900 -2
+ Misses 4657 4653 -4
- Partials 458 461 +3
|
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.
Do we properly use the flag afterward to not watch inbounds for the chain?
Yeah. It is used in below places by observer to pause |
…-disable-chain-by-IsSupported-flag
Description
The BSC Testnet was already disabled by setting
IsSupported = false
in chain parameter, but the zetaclient continues printing logs ofobserveInTX: lasstScanned heights for chain 97 ZetaSent 40544345 ERC20Deposited 40544345 TssRecvd 40544345
.This means zetaclients were still observing BSC Testnet. After checking logs in Datadog, I noticed below log print is the place which prevents the
IsSupported
flag to be updated in the zetaclient's context, and the observation of outbound/inbound were not paused properly.Closes:
Type of change
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Include instructions and any relevant details so others can reproduce.
Checklist: