Fix panic due to early onEvent Logger call in Zookeeper event handling #1028
+74
−78
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit removes the Logger call from the
onEventmethod in the Zookeeper event handling code.Previously, invoking
p.cluster.Logger()before theclusterwas fully resolved led to a runtime panic error (panic: runtime error: invalid memory address or nil pointer dereference).This change is a workaround to avoid the immediate crash.
I think you need to refactor the initialization sequence of the "provider" and its dependencies to ensure that the "cluster" is available before any event processing takes place.