-
Notifications
You must be signed in to change notification settings - Fork 193
chore: fix formatting issues in logp printf-style calls #9757
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
Conversation
This pull request does not have a backport label. Could you fix it @khushijain21? 🙏
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
|
💛 Build succeeded, but was flaky
Failed CI Steps |
Strange that CI did not complain about this single case in my previous PR. Thanks for fixing it! |
@Mergifyio backport 9.0 9.1 |
✅ Backports have been created
|
(cherry picked from commit a47be25)
(cherry picked from commit a47be25)
(cherry picked from commit a47be25)
(cherry picked from commit a47be25) Co-authored-by: Khushi Jain <[email protected]>
(cherry picked from commit a47be25) Co-authored-by: Khushi Jain <[email protected]>
(cherry picked from commit a47be25) Co-authored-by: Khushi Jain <[email protected]>
Proposed commit message
This PR fixes fatal go vet errors on calls to logp functions. Release v0.22.1 of elastic-agent-libs enabled proper go vet support for printf style calls in logp, and that uncovered many misuses of printing directives.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test
Related issues