-
Notifications
You must be signed in to change notification settings - Fork 468
twilio-ruby 6.0 mangles .rbenv path #655
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
Comments
Ah, likely covered by #654 |
Thanks for the PR. We'll review it soon.Please expect the fix in upcoming release. |
Merged with 654. |
I hit this issue today. I know the fix is already merged, but: wouldn't it have been more reliable to just base_file = file.gsub(/\.rb$/, '_base.rb')
require base_file if File.exists?(base_file) ... In that wat you let the existence/absence of the base files drive the load behaviour, instead of having to duplicate the logic here and bake in the exception for |
I faced this issue today,
|
I faced the exact same issue as @Azzawie did,
|
The fix is merged, we're going to release it in the upcoming release this week. Meanwhile please use v5.77.0, if you're blocked by this. |
Hi everyone, we've released a new ruby version v6.0.1 with the fix. Please upgrade and let us know if you need further help. Thanks. Closing this thread, please feel free to open another issue, if this persists. |
Issue Summary
When using 6.0 in an rbenv/bundler setup, this line:
twilio-ruby/lib/twilio-ruby/rest.rb
Line 8 in 1956b94
mangles paths and thus twilio-ruby can't be used as
require "twilio-ruby"
This is because a path like this:
/Users/REDACTED/.rbenv/versions/2.7.8/lib/ruby/gems/2.7.0/gems/twilio-ruby-6.0.0/lib/twilio-ruby/rest/accounts.rb
gets turned into
/Users/REDACTED/.base_rbenv/versions/2.7.8/lib/ruby/gems/2.7.0/gems/twilio-ruby-6.0.0/lib/twilio-ruby/rest/accounts_base.rb
where the .rbenv gets modified into .base_rbenv (when the actual goal was just the filename getting that sub)
Steps to Reproduce
Code Snippet
n/a
Exception/Log
Technical details:
The text was updated successfully, but these errors were encountered: