-
Notifications
You must be signed in to change notification settings - Fork 442
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
[BUG] go.mod tidy fails due to unresolved module in dd-trace-go #3059
Comments
I encountered this issue as well. Downgrading OpenTelemetry made changes to the collector as they changed the profile name from The changes are in |
Hi. Is there an ETA on that issue? It is blocking us from upgrading packages in our repos. It seems like a critical issue, right? Since this version is not usable |
👋 Hello, happy new year and apologies everyone for the delay on this. We found a temporary fix that we merged in #3042 waiting for the right release from the agent team. You can already try running We are confident in getting |
I also want to know when the fix of this issue will be released. Especially now, when downgrading |
I see https://github.com/DataDog/dd-trace-go/actions/runs/12585119784/job/35076220193 still failing with the same error, although the fix from #3042 is already applied into that branch (
|
@rosti-il This job tests dd-trace-go against https://github.com/DataDog/orchestrion and we need to upgrade |
I can confirm [email protected] is now released which why I will now close this issue. Feel free to reopen it if for some reason this error comes up again. |
@eliottness Thank you. The [email protected] works for me! |
Version of dd-trace-go
gopkg.in/DataDog/dd-trace-go.v1 v1.70.1
Describe what happened:
When adding the following import statement in a Go file:
and running
go get -u -t ./...
followed bygo mod tidy
, the following error occurs:Describe what you expected:
I expected
go mod tidy
to resolve all module dependencies and clean up the go.mod and go.sum files without encountering unresolved dependencies.Steps to reproduce the issue:
Additional environment details (Version of Go, Operating System, etc.):
go version go1.23.4 darwin/arm64
The text was updated successfully, but these errors were encountered: