Skip to content
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

contrib/internal/httptrace uses "inet.af/netaddr" which in turns imports go4.org/unsafe/assume-no-moving-gc #1405

Closed
mrkagelui opened this issue Aug 3, 2022 · 9 comments

Comments

@mrkagelui
Copy link
Contributor

Hi,

My app failed the test on the recent Go 1.19 because of go4.org/unsafe/assume-no-moving-gc, or rather because the current version used in this lib is not the latest, kindly check history of https://github.com/go4org/unsafe-assume-no-moving-gc/blob/main/untested.go for more info.

Here's part of my go mod why:

# go4.org/unsafe/assume-no-moving-gc
...
gopkg.in/DataDog/dd-trace-go.v1/contrib/net/http
gopkg.in/DataDog/dd-trace-go.v1/contrib/internal/httptrace
inet.af/netaddr
go4.org/intern
go4.org/unsafe/assume-no-moving-gc

My question is: why is inet.af/netaddr used instead of the standard package "net"?

If we really need it, could we upgrade to the latest "inet.af/netaddr" to use the latest unsafe package? ref: inetaf/netaddr@377050f

@Hellzy
Copy link
Contributor

Hellzy commented Aug 3, 2022

Hi @mrkagelui

My question is: why is inet.af/netaddr used instead of the standard package "net"?

This package has several features that are interesting to us that std "net" doesn't have.
An example: #1328 (comment).

I'd say let's go ahead with the upgrade.

@mrkagelui
Copy link
Contributor Author

thank you for the answer, will read

@Hellzy
Copy link
Contributor

Hellzy commented Aug 3, 2022

#1406 was merged, closing. Thanks for this @mrkagelui.

@Hellzy Hellzy closed this as completed Aug 3, 2022
@hbagdi
Copy link

hbagdi commented Aug 5, 2022

Is there a release planned including this fix?

@mrkagelui
Copy link
Contributor Author

Is there a release planned including this fix?

I think there's a milestone in that associated PR that says 1.41.0

@hbagdi
Copy link

hbagdi commented Aug 8, 2022

I'm not very familiar with this repository's development and release timelines.
Is it possible to get this shipped as part of the patch release?
We want to move to Go 1.19 and this issue holds that up. This is the last blocker for us and possibly others in the community.

@nsrip-dd
Copy link
Contributor

nsrip-dd commented Aug 8, 2022

We have tagged a release candidate for v1.41.0 which contains this fix:

go get gopkg.in/DataDog/dd-trace-go.v1@v1.41.0-rc.1

The full release should be out by the end of the week

@hbagdi
Copy link

hbagdi commented Aug 8, 2022

Sweet. Thanks!

@mrkagelui
Copy link
Contributor Author

I'm not very familiar with this repository's development and release timelines. Is it possible to get this shipped as part of the patch release? We want to move to Go 1.19 and this issue holds that up. This is the last blocker for us and possibly others in the community.

an alternative is to force upgrade, go get -u inet.af/netaddr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants