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
{{ message }}
This repository has been archived by the owner on Aug 30, 2023. It is now read-only.
Hey, maybe I'm doing something wrong or I'm missing some config or whatnot, but I'm not able to get source code context to appear in the Sentrt when running the compiled binary on another machine (typical use: build on CI, deploy to another server (bin only), run there). The paths are relative to where I built the binary and the source code is missing (I see only file/function names).
The text was updated successfully, but these errors were encountered:
Go binaries doesn't provide enough information to do that, as they are compiled down to machine code. It'd be possible to somehow perform mapping to external files, but environment running the binary would still need access to the corresponding files.
Absolutely, but it'd be better than nothing to be able to provide some source code if a user wants a mapping. Like the ability to add sourcemaps for JS.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey, maybe I'm doing something wrong or I'm missing some config or whatnot, but I'm not able to get source code context to appear in the Sentrt when running the compiled binary on another machine (typical use: build on CI, deploy to another server (bin only), run there). The paths are relative to where I built the binary and the source code is missing (I see only file/function names).
The text was updated successfully, but these errors were encountered: