[receiver/vcenter]Fix nil pointer exception when vcenter receiver collectVMs.#16278
Merged
Conversation
Fix nil pointer exception when vcenter receiver collectVMs.
Adjustment Change Log
djaglowski
reviewed
Nov 14, 2022
djaglowski
approved these changes
Nov 16, 2022
Member
|
LGTM, but there is a lint failure |
JaredTan95
pushed a commit
to openinsight-proj/opentelemetry-collector-contrib
that referenced
this pull request
Nov 21, 2022
…lectVMs. (open-telemetry#16278) Fix nil pointer exception when vcenter receiver collectVMs.
shalper2
pushed a commit
to shalper2/opentelemetry-collector-contrib
that referenced
this pull request
Dec 6, 2022
…lectVMs. (open-telemetry#16278) Fix nil pointer exception when vcenter receiver collectVMs.
Closed
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
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.
Description:
Fix nil pointer exception when vcenter receiver collectVMs.
Link to tracking Issue:
PR#16277
Testing:
Documentation: