Description
We use the following tech stack:
rails (7.0.5)
skylight (5.3.4)
sentry-rails (5.9.0)
sentry-ruby (5.9.0)
And unfortunately, we've been having some trouble with stack traces on Sentry getting super garbled. You can see the report on the sentry-ruby Github here: getsentry/sentry-ruby#1863
I explained a bit of what we were seeing in this comment here: getsentry/sentry-ruby#1863 (comment), but in a nutshell, stack traces look like the following:

Basically one good frame, and then a bunch of seemingly looping frames.
The lines I see regarding skylight and sentry in the garbled stack are:
skylight (5.3.4) lib/skylight/middleware.rb in call at line 99
sentry-rails (5.9.0) lib/sentry/rails/tracing.rb in instrument at line 54
skylight (5.3.4) lib/skylight/probes/action_dispatch/request_id.rb in call at line 8
When I disable Skylight's process_middleware.action_dispatch
Normalizer (e.g. https://github.com/skylightio/skylight-ruby/blob/master/lib/skylight/normalizers/action_dispatch/process_middleware.rb) it looks like the logs calm down, but I couldn't trace any further than that. Something with what the instrumenter is doing.
Just figured I'd submit this issue here as well, in case there was any insights that could be gleamed, although the issue seems to be the interaction of these two different libraries together.