Add missing initialized? checks to sentry-rails

[sl0thentr0py]

The at_exit Sentry.close call might cause these Sentry.get_current_scopes to return nil and break some setups.

Fixes #1885

[st0012]

Can you add a changelog entry too? Thx

[sl0thentr0py]

I always forget the changelog :(
I'm thinking of adding a bot for this.
Relay uses https://github.com/getsentry/relay/blob/master/.github/workflows/danger.yml

[st0012]

I thought about using GH's release to automatically generate changelogs, but it doesn't fit our release flow (having changelog before releasing).
I'd be happy to try the workflow you mentioned 👍

[sl0thentr0py]

@st0012 craft actually supports changelog: auto on release but I'm not happy with the quality of the generated changelogs (lots of noise). I actually like your changelogs a lot, so I want to keep doing it this way here. :)

[st0012]

@sl0thentr0py Thanks for your kind words ❤️

[cleptric]

Sorry to chime in, but the Ruby SDK changelogs are a staple at Sentry. Pls keep this 🚀

[gareth]

This code generates a LocalJumpError: unexpected return error in my install. I'm pulling sentry-ruby from source to try and mitigate the same problem as in #1885, which shows up in our test environments. (It shows up even though we're not using guard, so the workaround from that issue didn't work for us)

I'm using Rails 6.1.6 with Ruby 2.7.6p219

Instead, using a basic conditional like this was enough to make our tests pass:

          if Sentry.initialized?
            Sentry.get_current_scope.set_transaction_name("#{controller.class}##{controller.action_name}", source: :view)
          end

[st0012]

ping @sl0thentr0py

[sl0thentr0py]

oof my bad, thx @gareth

[sl0thentr0py]

#1926