Skip to content
New issue

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

Change in require behaviour with latest 5.4.0 version. #1856

Closed
jkogara opened this issue Jul 26, 2022 · 2 comments · Fixed by #1857
Closed

Change in require behaviour with latest 5.4.0 version. #1856

jkogara opened this issue Jul 26, 2022 · 2 comments · Fixed by #1857
Assignees

Comments

@jkogara
Copy link

jkogara commented Jul 26, 2022

Issue Description

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

Reproduction Steps

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

[ |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)

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

@sl0thentr0py
Copy link
Member

sl0thentr0py commented Jul 26, 2022

fixing asap, thx for reporting! this was due to #1825

@sl0thentr0py
Copy link
Member

@jkogara released 5.4.1, sorry about that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
@jkogara @st0012 @sl0thentr0py and others