Stan Lo

https://github.com/getsentry/sentry-ruby/issues/1570 looks pretty similar to what you propose here but with more detail. Would you say it matches your expectation?

@manme I see. What'll happen after the first report then? In your example, the SDK should send the event after the 4th retry failed, right?. After that, should it send...

Sorry for the delay. I think this is helpful but may cause issue with the `async` option, which we plan to drop in `v6.0.0`. I'll revisit this after it's dropped.

@stanhu this was implemented in the old sentry-raven SDK but not the new sentry-ruby. I’ll think about adding it. Thanks for the proposal 🙂

@coffenbacher I've done a similar feature in my [gem](https://github.com/st0012/power_trace). The differences are: 1. my gem collects all frames' info right away, instead of just storing callers. because the callers (call...

I wouldn't say it's Ruby's "issue". It's just a feature that Ruby doesn't support so you need to pay extra cost for the additional implementation. IMO, the best way to...

fyi, I'm adding a partial support of this feature in https://github.com/getsentry/sentry-ruby/pull/1580

@mecampbellsoup it's available on master and you can try it whenever you want to 😄 I've activated in my work project for 2 weeks and haven't seen any issue. I'm...

yeah it'll be included in `4.8.0`. you can check the [changelog](https://github.com/getsentry/sentry-ruby/blob/master/CHANGELOG.md#features) for usage.

Hmm not really because: 1. It's not enabled by default. So many users may even not be aware of it. 2. ATM, `TracePoint` cancels YJIT's optimization so for newer Ruby...