-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cherry-pick #23770 to 7.x: Update go-concert to 0.1.0 #24050
Conversation
Pinging @elastic/integrations-services (Team:Services) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪Steps errors
Expand to view the steps failures
|
Test | Results |
---|---|
Failed | 0 |
Passed | 46507 |
Skipped | 4841 |
Total | 51348 |
l.Listener.Close() | ||
}() | ||
|
||
l.log.Info("Started listening for " + l.family.String() + " connection") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code-block should not have existed in 7.x. Maybe some older backport that didn't go well.
Removing this block fixes:
- reduce chance for leaking resources due to an existing context being overwritten
- remove duplicate log message.
(cherry picked from commit 342a845)
6e9dfc2
to
3b05dd2
Compare
Cherry-pick of PR #23770 to 7.x branch. Original message:
What does this PR do?
Update go-concert to version 0.1.0 and update some code in Beats.
Why is it important?
Uhm... UPDATES \o/
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature works- [ ] I have added an entry inCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.