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

node: Fix false negative connection to FS chain in multi-endpoint setup #2987

Merged
merged 1 commit into from
Oct 29, 2024

Conversation

cthulhu-rider
Copy link
Contributor

Defect of 0d08b51. Previously, node unconditionally visited all configured FS chain endpoints, and the result of the connection to the last address was final. In the case where the previous nodes (at least one) were available but the last one was not, a general init error occurred.

Now node breaks on first successful dial.

Fixes #2986.

Copy link

codecov bot commented Oct 29, 2024

Codecov Report

Attention: Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Project coverage is 22.89%. Comparing base (7e0f04f) to head (8597a10).
Report is 2 commits behind head on master.

Files with missing lines Patch % Lines
pkg/morph/client/constructor.go 0.00% 1 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2987   +/-   ##
=======================================
  Coverage   22.88%   22.89%           
=======================================
  Files         785      785           
  Lines       58778    58779    +1     
=======================================
+ Hits        13454    13457    +3     
+ Misses      44443    44442    -1     
+ Partials      881      880    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@roman-khimov roman-khimov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Legit, changelog please.

Defect of 0d08b51. Previously, node
unconditionally visited all configured FS chain endpoints, and the
result of the connection to the last address was final. In the case
where the previous nodes (at least one) were available but the last one
was not, a general init error occurred.

Now node breaks on first successful dial.

Fixes #2986.

Signed-off-by: Leonard Lyubich <leonard@morphbits.io>
@roman-khimov roman-khimov merged commit 3d50ef8 into master Oct 29, 2024
20 of 21 checks passed
@roman-khimov roman-khimov deleted the bugfix/2986-fschain-recon branch October 29, 2024 14:53
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.

Node fails to connect to secondary RPCs during startup
2 participants