-
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
[Feature]: Migrate to go 1.20 #4202
Comments
Files to change:
|
In this commit, all the files mentioned in issue jaegertracing#4202 have been updated with Go version 1.20 replacing version 1.19
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]>
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]>
PR for the issue has already been made and would be merged during the next Release Cycle. |
👍 |
## Which problem is this PR solving? - Resolves #4202 ## 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]> --------- Signed-off-by: Saarthak <[email protected]> Co-authored-by: Yuri Shkuro <[email protected]>
## 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]>
I opened #4328 to suggest partially reverting the changes on #4206 so that Jaeger remains compatible with Go 1.19 as a library. This would help the OpenTelemetry Collector project, which aims to be compatible with all officially supported Go versions. Note that after my PR binaries would still be built with Go 1.20 which I think would fulfill the goals that @scalalang2 talks about in this issue, this is only about using Jaeger as a library. Please consider my PR! :) |
Requirement
Go 1.20 officially released today
There's improvements on the garbage collector. It informs that its overall performace improves by up to 2% and reduces memory overheads. I guess that migrating to go 1.20 will provides improved performance, bug fixes, security enhancements and etc.
Problem
There's no problem on Jaeger.
This proposal only include a simple suggestion.
Thanks.
Proposal
Migrate to go runtime 1.20.
Open questions
No response
The text was updated successfully, but these errors were encountered: