-
Notifications
You must be signed in to change notification settings - Fork 219
fix: default stop handler exists only if informer started #1575
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
Conversation
@@ -41,7 +41,7 @@ class InformerRelatedBehaviorITS { | |||
KubernetesClient adminClient = new KubernetesClientBuilder().build(); | |||
InformerRelatedBehaviorTestReconciler reconciler; | |||
String actualNamespace; | |||
volatile boolean stopHandlerCalled = false; | |||
volatile boolean stopHandlerCalledReplacement = false; |
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.
Why replacement
?
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.
well, there is a default one originally
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.
volatile boolean stopHandlerCalledReplacement = false; | |
volatile boolean replacementStopHandlerCalled = false; |
would be more correct, imo, then.
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.
changed from IDE
Kudos, SonarCloud Quality Gate passed! |
No description provided.