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 #80578

Merged
merged 2 commits into from
Nov 12, 2024

Conversation

loewenheim
Copy link
Contributor

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.

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 requested review from a team as code owners November 12, 2024 09:41
@github-actions github-actions bot added Scope: Frontend Automatically applied to PRs that change frontend components Scope: Backend Automatically applied to PRs that change backend components labels Nov 12, 2024
Copy link
Contributor

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

@loewenheim loewenheim changed the title feat(symbolication): Introduce "unsupported dsym" error (#80517) feat(symbolication): Introduce "unsupported dsym" error Nov 12, 2024
@loewenheim loewenheim enabled auto-merge (squash) November 12, 2024 09:52
Copy link

codecov bot commented Nov 12, 2024

Codecov Report

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

✅ All tests successful. No failed tests found.

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   #80578      +/-   ##
==========================================
- Coverage   78.36%   78.36%   -0.01%     
==========================================
  Files        7206     7206              
  Lines      318720   318723       +3     
  Branches    43905    43906       +1     
==========================================
- Hits       249771   249760      -11     
- Misses      62589    62598       +9     
- Partials     6360     6365       +5     

@loewenheim loewenheim merged commit 37db654 into master Nov 12, 2024
55 checks passed
@loewenheim loewenheim deleted the feat/unsupported-dsym branch November 12, 2024 10:24
@github-actions github-actions bot locked and limited conversation to collaborators Nov 27, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components Scope: Frontend Automatically applied to PRs that change frontend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants