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

morph: fix nil pointer dereferencing to connection #3073

Merged
merged 1 commit into from
Dec 27, 2024

Conversation

End-rey
Copy link
Contributor

@End-rey End-rey commented Dec 26, 2024

When the RPC connection is lost and a recovery attempt occurs, the variable conn responsible for the connection may be nil and therefore additional verification is needed.

I couldn't come up with a better solution, so I'm open to smart thoughts.

Closes #3061.

Copy link

codecov bot commented Dec 26, 2024

Codecov Report

Attention: Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.

Project coverage is 22.42%. Comparing base (fb304b4) to head (48d09ab).
Report is 2 commits behind head on master.

Files with missing lines Patch % Lines
pkg/morph/client/multi.go 0.00% 3 Missing ⚠️
pkg/morph/client/notifications.go 0.00% 2 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #3073   +/-   ##
=======================================
  Coverage   22.42%   22.42%           
=======================================
  Files         792      792           
  Lines       58535    58538    +3     
=======================================
+ Hits        13129    13130    +1     
- Misses      44505    44507    +2     
  Partials      901      901           

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

@End-rey End-rey force-pushed the 3061-panic-sighup-switch-rpc-node branch from e6a0a4e to 5df74ac Compare December 26, 2024 19:55
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.

The fix itself is exactly it.

CHANGELOG.md Outdated Show resolved Hide resolved
@End-rey End-rey force-pushed the 3061-panic-sighup-switch-rpc-node branch from 5df74ac to 1e7896e Compare December 26, 2024 20:05
@roman-khimov
Copy link
Member

Needs a rebase because of CHANGELOG conflict.

When the RPC connection is lost and a recovery attempt occurs, the variable
`conn` responsible for the connection may be nil and therefore additional
verification is needed.

Closes #3061.

Signed-off-by: Andrey Butusov <[email protected]>
@End-rey End-rey force-pushed the 3061-panic-sighup-switch-rpc-node branch from 1e7896e to 48d09ab Compare December 27, 2024 08:51
@roman-khimov roman-khimov merged commit 08bd8d3 into master Dec 27, 2024
20 of 22 checks passed
@roman-khimov roman-khimov deleted the 3061-panic-sighup-switch-rpc-node branch December 27, 2024 09:08
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.

panic during node sighup processing in case of problems with rpc node
2 participants