Issue Description
7b00b25 introduced invocations of Gem::Specification.find_by_name, which doesn't work when using bundler standalone. This means that this release will cause production issues for people that use bundler standalone.
/Users/my-username/.asdf/installs/ruby/3.3.1/lib/ruby/3.3.0/rubygems/dependency.rb:313:in `to_specs': Could not find 'sentry-ruby' (>= 0) among 333 total gem(s) (Gem::MissingSpecError)
Checked in 'GEM_PATH=/Users/my-username/.gem/ruby/3.3.0:/Users/my-username/.asdf/installs/ruby/3.3.1/lib/ruby/gems/3.3.0' , execute `gem env` for more information
from /Users/my-username/.asdf/installs/ruby/3.3.1/lib/ruby/3.3.0/rubygems/dependency.rb:325:in `to_spec'
from /Users/my-username/.asdf/installs/ruby/3.3.1/lib/ruby/3.3.0/rubygems/specification.rb:1023:in `find_by_name'
from /Users/my-username/Source/my-project/gems/ruby/3.3.0/gems/sentry-rails-5.18.0/lib/sentry/rails/tracing/active_record_subscriber.rb:16:in `<class:ActiveRecordSubscriber>'
from /Users/my-username/Source/my-project/gems/ruby/3.3.0/gems/sentry-rails-5.18.0/lib/sentry/rails/tracing/active_record_subscriber.rb:6:in `<module:Tracing>'
from /Users/my-username/Source/my-project/gems/ruby/3.3.0/gems/sentry-rails-5.18.0/lib/sentry/rails/tracing/active_record_subscriber.rb:5:in `<module:Rails>'
from /Users/my-username/Source/my-project/gems/ruby/3.3.0/gems/sentry-rails-5.18.0/lib/sentry/rails/tracing/active_record_subscriber.rb:4:in `<module:Sentry>'
from /Users/my-username/Source/my-project/gems/ruby/3.3.0/gems/sentry-rails-5.18.0/lib/sentry/rails/tracing/active_record_subscriber.rb:3:in `<main>'
from <internal:/Users/my-username/.asdf/installs/ruby/3.3.1/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
Reproduction Steps
No time right now, having to deal with the issues created by this new release.
Expected Behavior
It doesn't crash when using bundler standalone
Actual Behavior
It crashes
Ruby Version
3.3.1
SDK Version
5.18.0
Integration and Its Version
No response
Sentry Config
No response
Issue Description
7b00b25 introduced invocations of
Gem::Specification.find_by_name, which doesn't work when using bundler standalone. This means that this release will cause production issues for people that use bundler standalone.Reproduction Steps
No time right now, having to deal with the issues created by this new release.
Expected Behavior
It doesn't crash when using bundler standalone
Actual Behavior
It crashes
Ruby Version
3.3.1
SDK Version
5.18.0
Integration and Its Version
No response
Sentry Config
No response