-
Notifications
You must be signed in to change notification settings - Fork 183
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 nats reconnects #8880
Fix nats reconnects #8880
Conversation
Signed-off-by: jkoberg <[email protected]>
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.
Please change the changelog message wording. Other than that I am fine with it.
natsOptions.ReconnectedCB = func(_ *nats.Conn) { | ||
if err := n.Init(); err != nil { | ||
fmt.Println("cannot reconnect to nats") | ||
os.Exit(1) |
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.
💥 OUCH
I guess I understand why you're doing that. And I don't have a better solution at hand. But I still feel the need to say: This is ugly 😄
Would be nice if we could find a way for a more graceful error handling here.
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.
Yes I 100% agree. ❤️ I'll fix it as soon as we have a proper solution.
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.
LGTM, but now Sonarcloud doesn't like you anymore ...
Co-authored-by: Ralf Haferkamp <[email protected]> Signed-off-by: jkoberg <[email protected]>
Quality Gate passedIssues Measures |
No code changes - just force pushed to restart sonarcloud. |
@micbar Why do think it could be problematic regarding semver? It's a bugfix. It doesn't need new config. Neither does it break existing setups (does it?). |
then let us backport. |
Repairs reconnects on the natsjs kv registry
New behaviour:
Fixes #8783