Closed cr7258 closed 4 days ago
https://github.com/alibaba/opentelemetry-go-auto-instrumentation/issues/67 use go clean --cache
to get rid of this. @y1yang0 https://github.com/alibaba/opentelemetry-go-auto-instrumentation/pull/78 This PR doesn't seem to be working, should we point it out in document?
https://github.com/alibaba/opentelemetry-go-auto-instrumentation/issues/203, we will point it out in document
67 use
go clean --cache
to get rid of this. @y1yang0 #78 This PR doesn't seem to be working, should we point it out in document?
I will document it and add it back. It was removed because its inclusion would cause test problems. This time, I will thoroughly analyze these problems .
Describe the bug
I have a simple go file.
When I ran the
go run
command to run the program, it printed a single line as expected.However, after I run the
otel go build
command, the go binary seems to be hacked. Even if I just want to simply run the program, otel will also intervene.Steps to reproduce
Run
otel go build
command first, then rungo build
command.Expected behavior
otel
shouldn't intervene when I didn't add theotel
prefix to the command.Actual behavior
otel
always intervenes even if I didn't add theotel
prefix to the command.opentelemetry-go-auto-instrumentation version
otel version 1.0.0_94b8b9f (I build it from the latest main branch)
Environment
Go: go version go1.22.1 darwin/arm64 OS: MacOS 15.1
Additional context
No response