We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have an in house gem that wraps the sentry library. Before the 5.4.0 release
require 'sentry-ruby'
loaded the sentry library, this now raises the following exception
LoadError: cannot load such file -- sentry-ruby
Add sentry-ruby as a runtime dependency to a newly created gem. Add require 'sentry-ruby' to the entry point to the gem run ./bin/console
sentry-ruby
./bin/console
[ |main S:15 U:2 ?:1 ✗|]» ./bin/console Traceback (most recent call last): 3: from ./bin/console:5:in `<main>' 2: from ./bin/console:5:in `require' 1: from /home/jkogara/src/hopin/tesy-sentry/lib/tesy/sentry.rb:4:in `<top (required)>' /home/jkogara/src/hopin/tesy-sentry/lib/tesy/sentry.rb:4:in `require': cannot load such file -- sentry-ruby (LoadError)
It should load without exception
There is an exception
2.7.2p137
5.4.0
No response
The text was updated successfully, but these errors were encountered:
fixing asap, thx for reporting! this was due to #1825
Sorry, something went wrong.
spec.files
sentry-ruby.gemspec
@jkogara released 5.4.1, sorry about that!
st0012
Successfully merging a pull request may close this issue.
Issue Description
I have an in house gem that wraps the sentry library. Before the 5.4.0 release
loaded the sentry library, this now raises the following exception
Reproduction Steps
Add
sentry-ruby
as a runtime dependency to a newly created gem.Add
require 'sentry-ruby'
to the entry point to the gemrun
./bin/console
Expected Behavior
It should load without exception
Actual Behavior
There is an exception
Ruby Version
2.7.2p137
SDK Version
5.4.0
Integration and Its Version
No response
Sentry Config
No response
The text was updated successfully, but these errors were encountered: