You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running this inspection on a binary built with go build and go.mod, we are able to see the deps in the executable. However, when inspecting an executable built with bazel, the deps are not there.
I'm running into the same issue where bazel built binaries do not return anything when executing go version -m <path-to-bin> but binaries built with go build return all the embedded modules and their versions.
We can inject data, but it's not clear what data that should be. Bazel Go targets can depend on Go code that isn't even a Go module. PRs that wire this up in any reasonable way are welcome though, I'm happy to support them as well.
Hi,
Me and https://github.com/RonFed are working on OpenTelemetry auto instrumentation module. This issue is regarding the one here
In order to correctly instrument a go binary, we need to extract the dependencies and their versions from the executable file.
We use the
debug/buildinfo
from the standard library, doing something similar to this:When running this inspection on a binary built with
go build
andgo.mod
, we are able to see the deps in the executable. However, when inspecting an executable built with bazel, the deps are not there.Example sections from our build configuration:
BUILD.bazel
deps.bzl
How can we get this info from a binary built with bazel? Any help will be appreciated
The text was updated successfully, but these errors were encountered: