-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Update Go version to 1.20 #4206
Update Go version to 1.20 #4206
Conversation
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.
Thanks! Please make sure that all commits (or squash into one) are signed per CONTRIBUTING.md
All the files mentioned in issue jaegertracing#4202 have been updated with Go version 1.20 replacing version 1.19 Signed-off-by: Saarthak <[email protected]>
78f4f84
to
8e48e04
Compare
I have signed the DCO as required! Thank You Very Much for reviewing the changes |
I think the unit test failures relate to golangci-lint incompatibility with go 1.20. We can try upgrading to golangci-lint v1.51.0 in the Makefile here. |
Updates the Makefile to make golangci-lint compatible with Go v1.20 Signed-off-by: Saarthak <[email protected]>
Linter failing Error: cmd/anonymizer/app/query/query.go:83:3: S1011: should replace loop with |
Use a single \'append\' to concatenate two slices ie No for loop required Signed-off-by: Saarthak <[email protected]>
Linter was failing due to check S1011 I have made the necessary changes |
…o_version_update
There was a merge conflict which was happening, so I pulled the latest changes from the main repo to my fork, then git pull (ed) the changes to the branch I'm working in locally, and then after merging the changes I pushed it again to Github The previous update with merge conflict was giving Unit Test error and Kafka error |
The Unit Tests seem to be failing with exit code 2 What I have speculated is that:
Please let me know some suggestions and problems which I might be making for the same Thank You! |
I see this error in the output
|
try running |
I'm getting the following error on running I came across this article and am currently trying to solve it this way Thank you for reviewing the changes and helping me along the way! |
Signed-off-by: Saarthak <[email protected]>
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## main #4206 +/- ##
==========================================
- Coverage 97.09% 97.07% -0.03%
==========================================
Files 302 302
Lines 17685 17685
==========================================
- Hits 17172 17168 -4
- Misses 413 416 +3
- Partials 100 101 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Thanks. I'm not going to merge it just yet, but for the next release. |
## Which problem is this PR solving? - Resolves jaegertracing#4202 ## Short description of the changes All the files mentioned in issue jaegertracing#4202 have been updated with Go version 1.20 replacing version 1.19 Signed-off-by: Saarthak Maini <[email protected]> --------- Signed-off-by: Saarthak <[email protected]> Co-authored-by: Yuri Shkuro <[email protected]> Signed-off-by: shubbham1215 <[email protected]>
This partially reverts jaegertracing#4206. On the OpenTelemetry Collector project we aim to provide support for all officially supported Go versions. Per Go's support policy [1], Go 1.19 will remain a supported Go version until Go 1.21 is released. Since we take a dependency on Jaeger as a library, we need Jaeger to remain compatible with Go 1.19 as a library to be able to keep it updated. This patch does not revert other changes on jaegertracing#4206; Jaeger binaries would continue to be built with Go 1.20 and benefit from all performance and security improvements that the 1.20 release cycle offers. Signed-off-by: Pablo Baeyens <[email protected]>
Which problem is this PR solving?
Short description of the changes
All the files mentioned in issue #4202 have been updated with Go version 1.20 replacing version 1.19
Signed-off-by: Saarthak Maini [email protected]