Skip to content
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

Merged
merged 5 commits into from
May 23, 2024

Conversation

ws4charlie
Copy link
Contributor

Description

The BSC Testnet was already disabled by setting IsSupported = false in chain parameter, but the zetaclient continues printing logs of observeInTX: 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.

image

Closes:

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

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.

  • Tested CCTX in localnet
  • Tested in development environment
  • Go unit tests
  • Go integration tests
  • Tested via GitHub Actions

Checklist:

  • I have added unit tests that prove my fix feature works

Copy link

codecov bot commented May 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.06%. Comparing base (803658d) to head (d09ebd2).

Additional details and impacted files

Impacted file tree graph

@@           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     
Files Coverage Δ
zetaclient/zetacore/client.go 42.13% <ø> (-0.46%) ⬇️

Copy link
Member

@lumtis lumtis left a 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?

@ws4charlie
Copy link
Contributor Author

ws4charlie commented May 22, 2024

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

  1. bitcoin inbound
  2. bitcoin outbound
  3. bitcoin inbound trackers
  4. evm inbound
  5. evm outbound
  6. evm inbound trackers

@ws4charlie ws4charlie merged commit 1302dcc into develop May 23, 2024
21 checks passed
@ws4charlie ws4charlie deleted the fix-disable-chain-by-IsSupported-flag branch May 23, 2024 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants