-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Only keep in stack trace referenced debug images #46494
Only keep in stack trace referenced debug images #46494
Conversation
Remove the debug images not referenced in the stack trace so the debug images don't contain customer data. Fixes GH-46174
Co-authored-by: Joris Bayer <[email protected]>
Co-authored-by: Joris Bayer <[email protected]>
🚨 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 |
I only need a review from @jjbayer.
Sorry about the review mess caused by merging master into feature branches 😅😬.
This PR is opened against the https://github.com/getsentry/sentry/tree/feat/sdk-crash-monitoring integration branch for #44342. The changes in this PR will not be deployed. A quick review from @jjbayer should be sufficient.
Remove the debug images not referenced in the stack trace so the debug images don't contain customer data.
Fixes GH-46174