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 resiliency in connect_all mode #54

Merged
merged 2 commits into from
Aug 9, 2022

Conversation

gilbertwong96
Copy link
Contributor

The tuple Freeze is different from the Members, which is the root cause why
reconnect mechanism out of work in connect_all mode.

This bug is introduced in #41.

The tuple `Freeze` is different from the `Members`, which is the root cause why
reconnect mechanism out of work in `connect_all` mode.

This bug is introduced in zhongwencool#41.
@gilbertwong96 gilbertwong96 changed the title Fix resiliency in connect_all Fix resiliency in connect_all mode Aug 9, 2022
@zhongwencool
Copy link
Owner

LGTM, Please help to update version from 0.3.5 to 0.3.6 :0

@gilbertwong96
Copy link
Contributor Author

LGTM, Please help to update version from 0.3.5 to 0.3.6 :0

Done

@zhongwencool zhongwencool merged commit c0d7181 into zhongwencool:master Aug 9, 2022
@gilbertwong96 gilbertwong96 deleted the hotfix/resiliency branch August 9, 2022 09:32
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