Cherry-pick #21882 to 7.x: Fix panic on add_docker_metadata close#21889
Merged
jsoriano merged 1 commit intoelastic:7.xfrom Oct 16, 2020
Merged
Cherry-pick #21882 to 7.x: Fix panic on add_docker_metadata close#21889jsoriano merged 1 commit intoelastic:7.xfrom
jsoriano merged 1 commit intoelastic:7.xfrom
Conversation
If the processor was not properly initialized, for example because it couldn't access the docker socket, then the watcher will be nil. Avoid trying to stop the watcher in that case. (cherry picked from commit 80b8f53)
Contributor
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
ChrsMark
approved these changes
Oct 16, 2020
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
|
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
3 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.
Cherry-pick of PR #21882 to 7.x branch. Original message:
If the processor was not properly initialized, for example because it
couldn't access the docker socket, then the watcher will be nil. Avoid
trying to stop the watcher in that case.
No changelog needed as the change introducing this issue hasn't
been released.
Related issues