-
-
Notifications
You must be signed in to change notification settings - Fork 211
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
Support for Source Context #646
Comments
We could use @Swatinem said:
|
@ashwoods lets make this a proper initiative so we can design this properly. |
Adding
I guess there's something that need to change on the server @Swatinem ? |
Well, yes :-) Sources embedded in the Portable PDB are not implemented at all. We would need to add support for that on the server side. I don’t think you can create a sentry "source bundle" directly from portable pdb files currently. Using the source embedded in the Portable PDB might be interesting, then you wouldn’t need a separate file either. |
Mind creating an issue in the appropriate repo so that it's tracked and eventually prioritized? I guess you'd be able to best describe what's needed. |
Here it is: getsentry/symbolic#725 |
The second approach, i.e. Tested manually on a local copy & the #2050 branch - works fine: https://sentry.io/organizations/sentry-sdks/issues/3744250864/events/9507e239323340909c12049cc24e7cf3/?project=5428537 |
Symbolicator PR: getsentry/symbolicator#996 - deployed to sentry.io on 2023-30-01 |
Both options work now on sentry.io
|
There are different approaches we can take to add support for source context:
It's possible to embed sources in the pdb. Couldn't find docs but general GitHub issues. Seems the property is
<Embed>true</Embed>
.With this approach we can document this on docs.sentry.io and suggest users opt-in. And read the source when capturing the SDK (opt-in at first, with the goal of making it opt-out). With the source embedded, we can read it at runtime (see this commit: 518ab64) and send it with the event.
Additional approach is to use Source Bundles and corresponding docs. This requires changes on Sentry CLI and the backend.
Yet another way is to support sourcelink on the server by fetching the external VCS repository to get the relevant line numbers. Related: When sourcelink data is available send with event #400 It also requires changes on the backend but can help us show source context for external, .NET libraries which commonly use sourcelink (.NET itself uses it).
Related:
getsentry/sentry-dart#132
getsentry/sentry-java#633
The text was updated successfully, but these errors were encountered: