Skip to content
This repository has been archived by the owner on Aug 30, 2023. It is now read-only.

Code context when deploying only binary #249

Open
grongor opened this issue Apr 6, 2019 · 3 comments
Open

Code context when deploying only binary #249

grongor opened this issue Apr 6, 2019 · 3 comments

Comments

@grongor
Copy link

grongor commented Apr 6, 2019

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).

image

@micahcoffman
Copy link

micahcoffman commented Apr 22, 2019

+1 on being able to resolve context somehow when binary is compiled in CI and run as elsewhere

@kamilogorek
Copy link
Contributor

kamilogorek commented Apr 23, 2019

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.

@micahcoffman
Copy link

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants