-
-
Notifications
You must be signed in to change notification settings - Fork 493
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
Deprecate capture_exception_frame_locals
in favour of includeLocalVariables
#1986
Comments
I actually prefer deprecating this feature until better APIs are provided by Ruby. Because the current implementation uses |
Could we think about turning it off by default in the next major, but still giving users the option to turn it on? |
Oh it's already off by default because there's always a concern on potential impact on performance. But now I'd actually discourage people from using it if they're on newer Rubies. It also depends on how much we want to prioritise this feature in the longer-term. If it's something we want every language to support, we can invest more time on shaping the Ruby APIs and hope it'd be shipped in Ruby 3.3. |
From talking with Sentry users it's a pretty high value add for debugging, since it can add a lot of context into current app state. We regularly get feedback around people thinking it's high value (though this does tend to be for the Python ecosystem, maybe this is different in Ruby land). In general I think it's important for us to prioritize this.
That's my bad, thought this worked like PHP and Python. It's also off by default for Node as well at the moment!
It would be great if we could invest in the core Ruby ecosystem and get this in a better state. Is there any way we at Sentry can help with to make that smoother? |
Yeah I agree that it's very valuable to have and that's why I implemented the current version. Glad to hear that it's been proven popular in other communities!
It has 2 stages:
|
@st0012 Let us know how we can support you (or generally) in this effort. Sentry needs this :) |
Some updates about this feature:
So to summarise what we have now:
I also want to say that cancelling YJIT's optimisation in the above case probably won't the end of the world. It's still largely depending on:
|
Since there's no immediate need to deprecate the feature, I opened #1993 for renaming. |
With getsentry/develop#813 merging in, we want to name the option
includeLocalVariables
in the Ruby SDK.The text was updated successfully, but these errors were encountered: