Skip to content
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

feat(symbolication): Introduce "unsupported dsym" error #80517

Merged
merged 1 commit into from
Nov 11, 2024

Conversation

loewenheim
Copy link
Contributor

This is intended to improve the user experience for cases like getsentry/symbolicator#1539 in which we attempt to symbolicate a CLR event with a Windows PDB file. It maps the "unsupported" frame status returned by Symbolicator (getsentry/symbolicator#1541) to a new error variant. Properly displaying and explaining this error is left for a future PR.

This is intended to improve the user experience for
cases like getsentry/symbolicator#1539
in which we attempt to symbolicate a CLR event with a Windows PDB
file. It maps the "unsupported" frame status returned by Symbolicator
(getsentry/symbolicator#1541) to a new
error variant. Properly displaying and explaining this error
is left for a future PR.
@loewenheim loewenheim merged commit c00fabf into master Nov 11, 2024
49 of 50 checks passed
@loewenheim loewenheim deleted the feat/unsupported-dsym branch November 11, 2024 13:12
@loewenheim loewenheim added the Trigger: Revert Add to a merged PR to revert it (skips CI) label Nov 11, 2024
@getsentry-bot
Copy link
Contributor

PR reverted: 58684f0

getsentry-bot added a commit that referenced this pull request Nov 11, 2024
Copy link

codecov bot commented Nov 11, 2024

Codecov Report

Attention: Patch coverage is 33.33333% with 2 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/sentry/lang/native/processing.py 0.00% 1 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master   #80517      +/-   ##
==========================================
- Coverage   78.36%   78.35%   -0.02%     
==========================================
  Files        7204     7204              
  Lines      318728   318731       +3     
  Branches    43928    43929       +1     
==========================================
- Hits       249781   249732      -49     
- Misses      62597    62638      +41     
- Partials     6350     6361      +11     

loewenheim added a commit that referenced this pull request Nov 12, 2024
This is intended to improve the user experience for cases like
getsentry/symbolicator#1539 in which we
attempt to symbolicate a CLR event with a Windows PDB file. It maps the
"unsupported" frame status returned by Symbolicator
(getsentry/symbolicator#1541) to a new error
variant. Properly displaying and explaining this error is left for a
future PR.
@loewenheim
Copy link
Contributor Author

Reverted because two issues popped up during deploy (one, two). It's not obvious how they would be related, though.

loewenheim added a commit that referenced this pull request Nov 12, 2024
Take 2 of #80517.

This is intended to improve the user experience for cases like
getsentry/symbolicator#1539 in which we
attempt to symbolicate a CLR event with a Windows PDB file. It maps the
"unsupported" frame status returned by Symbolicator
(getsentry/symbolicator#1541) to a new error
variant. Properly displaying and explaining this error is left for a
future PR.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: Backend Automatically applied to PRs that change backend components Trigger: Revert Add to a merged PR to revert it (skips CI)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants