Skip to content

[client] Do not reconnect to mgm server in case of handler error #3856

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

Merged
merged 2 commits into from
May 21, 2025

Conversation

pappz
Copy link
Contributor

@pappz pappz commented May 21, 2025

Describe your changes

  • Do not reconnect to mgm server in case of handler error
  • Set to nil the flow grpc client to prevent double close call

Issue ticket number and link

Stack

Checklist

  • Is it a bug fix
  • Is a typo/documentation fix
  • Is a feature enhancement
  • It is a refactor
  • Created tests that fail without the change (if possible)
  • Extended the README / documentation, if necessary

Set to nil the flow grpc client to nil
lixmal
lixmal previously approved these changes May 21, 2025
@pappz pappz changed the title Do not reconnect to mgm server in case of handler error [client] Do not reconnect to mgm server in case of handler error May 21, 2025
Copy link

@pappz pappz marked this pull request as ready for review May 21, 2025 17:31
@pappz pappz merged commit 802a181 into main May 21, 2025
35 checks passed
@pappz pappz deleted the fix/handler-err branch May 21, 2025 18:18
@matanbaruch
Copy link

This PR is breaking netbird in version 0.45.1. netbird peers are dropping and not recovering

@mlsmaycon
Copy link
Collaborator

@matanbaruch can you please share the client logs that didn't recover?

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