Handle MavenMetadata parser result NPE as reported by community member #4285
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.
What's changed?
Prevent an NPE by adding a null check, and changing the API response to be nullable to handle it downstream.
What's your motivation?
A community member reported seeing an exception that I can't explain otherwise.
Have you considered any alternatives or workarounds?
Not yet; this was mostly a quick attempt at replicating the issue, which failed, and then a subsequent at preventing the issue to kick off discussion on what avenues to explore.
Any additional context
Tried to replicate this with a test using various values for the byte array, but none immediately lead to
MavenMetadata metadata
being null, as found in the stack trace above.In the surrounding code there seem to be some edge cases where it concerns Nexus specifically; I've asked if this is what the user has in their environment.