Null check for nullable response object#10029
Merged
Merged
Conversation
laurit
approved these changes
Dec 7, 2023
zeitlinger
pushed a commit
to zeitlinger/opentelemetry-java-instrumentation
that referenced
this pull request
Dec 12, 2023
laurit
pushed a commit
to laurit/opentelemetry-java-instrumentation
that referenced
this pull request
Jan 18, 2024
This file contains hidden or 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
2 participants
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.
bug fix as
responseobject is nullable and it will throw an NPE onresponse.getAwsResponse()in case of error response.[docker-java-stream--300619952] INFO application aws-sdk-v1 - STDERR: java.lang.NullPointerException: Cannot invoke "com.amazonaws.Response.getAwsResponse()" because "response" is null