GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing github.com — fix: use the null-guarded metrics field in the Controller constructor by csviri · Pull Request #3531 · operator-framework/java-operator-sdk Conversation
Collaborator
The constructor deliberately guards against a null but its last statement bypasses that guard and calls the getter again: so a Uses the already-resolved Part of #3517
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
13 of 16 tasks
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Pull request overviewFixes a controller-construction correctness bug in Changes:
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactionsUh oh!
There was an error while loading. Please reload this page.
csviri
commented
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. LGTM
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
csviri
marked this pull request as ready for review
The constructor deliberately guards against a null `Metrics`:
this.metrics = Optional.ofNullable(configurationService.getMetrics()).orElse(Metrics.NOOP);
but its last statement bypasses that guard and calls the getter again:
configurationService.getMetrics().controllerRegistered(this);
so a `ConfigurationService` whose `getMetrics()` returns null fails with a
NullPointerException during controller construction, which is exactly what
the guard three lines up is meant to prevent. `EventProcessor` applies the
same `!= null ? metrics : Metrics.NOOP` guard, so the codebase does treat
a null `Metrics` as reachable even though the interface default returns
`Metrics.NOOP`.
Uses the already-resolved `metrics` field instead.
csviri
force-pushed
the
fix/controller-null-metrics-guard
branch
from
40c0890 to
24dc42b
Compare
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Pull request overviewCopilot reviewed 1 out of 1 changed files in this pull request and generated no new comments. Suppressed comments (1)operator-framework-core/src/main/java/io/javaoperatorsdk/operator/processing/Controller.java:141
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactionsUh oh!
There was an error while loading. Please reload this page.
csviri
added a commit
to csviri/java-operator-sdk
that referenced
this pull request
…operator-framework#3531) The constructor deliberately guards against a null `Metrics`: this.metrics = Optional.ofNullable(configurationService.getMetrics()).orElse(Metrics.NOOP); but its last statement bypasses that guard and calls the getter again: configurationService.getMetrics().controllerRegistered(this); so a `ConfigurationService` whose `getMetrics()` returns null fails with a NullPointerException during controller construction, which is exactly what the guard three lines up is meant to prevent. `EventProcessor` applies the same `!= null ? metrics : Metrics.NOOP` guard, so the codebase does treat a null `Metrics` as reachable even though the interface default returns `Metrics.NOOP`. Uses the already-resolved `metrics` field instead.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reviewers
Copilot code review
Copilot
Copilot review effort
Applies to this pull request for everyone.Learn more about Copilot code review.
Uh oh!
There was an error while loading. Please reload this page. AssigneesNo one assignedLabels
None yet
ProjectsMilestoneNo milestoneDevelopmentSuccessfully merging this pull request may close these issues. Uh oh!
There was an error while loading. Please reload this page. 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. |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |