-
Notifications
You must be signed in to change notification settings - Fork 509
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
Add range of executing node to frames #761
Conversation
@@ -217,35 +216,6 @@ def test_with_locals_disabled(sentry_init, capture_events): | |||
) | |||
|
|||
|
|||
@pytest.mark.parametrize("integrations", [[], [ExecutingIntegration()]]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh damn, thanks! Seems like I overlooked this.
This pull request has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
I think this and #748 might as well be left closed unless getsentry/sentry#19924 is going to be reopened. |
thx @alexmojaki, I'm just bringing this repo back to life and had to do some bulk changes, sorry for the confusion/notification spam! |
Part of #748
When ExecutingIntegration is enabled, each frame in an exception traceback now contains new data that looks like this:
This can be used to highlight exactly what the frame was doing, rather than just a line. Actually doing this will also require work on the server.
The line numbers may actually go beyond the amount of context that's been included, I don't know if that's something we want to address at this stage.