We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This work depends on this SDK issue resolving.
If the customer uses in_app_include to set some frames as in-app we should not later destroy it with one of our enhancement rules.
in_app_include
For instance, the customer installed their code under their virtual env which ends up under site-packages which we then mark as not an in-app frame. (
site-packages
sentry/src/sentry/grouping/enhancer/enhancement-configs/[email protected]
Line 377 in e56c063
Once the SDK issue is fixed we can then determine which frames should not be tried for enhancement.
The text was updated successfully, but these errors were encountered:
Instead of this, we're going to work on #79482.
Sorry, something went wrong.
Superseded by #83603
No branches or pull requests
This work depends on this SDK issue resolving.
If the customer uses
in_app_include
to set some frames as in-app we should not later destroy it with one of our enhancement rules.For instance, the customer installed their code under their virtual env which ends up under
site-packages
which we then mark as not an in-app frame. (sentry/src/sentry/grouping/enhancer/enhancement-configs/[email protected]
Line 377 in e56c063
Once the SDK issue is fixed we can then determine which frames should not be tried for enhancement.
The text was updated successfully, but these errors were encountered: