You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chruby cannot successfully switch to mruby-3.0.0 under Fish, but seems to work as expected under Bash in spite of raising a Ruby NoMethodError exception when attempting to change rubies. The latter issue was raised upstream with chruby.
Steps To Reproduce
Steps to reproduce the bug:
ruby-install mruby-3.0.0
exec fish --login, which is required for chruby to pick up the newly installed Ruby
chruby mruby or chruby mruby-3.0.0
chruby, which shows that the selected Ruby hasn't changed
Expected Behavior
chruby-fish should not halt execution or report a different exit status than chruby itself. If the Ruby exception is not a show-stopper, then chruby-fish should not halt execution when the Bash version of chruby continues, and should change to the requested Ruby under the same circumstances that the Bash version of chruby does.
Actual Behavior
My default Ruby is currently set to Ruby 3.1.2. ruby-install mruby-3.0.0 succeeds without error. Under Bash, the following error still occurs:
$ bash --version | head -1
GNU bash, version 5.1.16(1)-release (x86_64-apple-darwin20.6.0)
$ chruby mruby
trace (most recent call last):
-:1: undefined method 'defined?' (NoMethodError)
but the current Ruby is changed to mruby-3.0.0, RUBY_ROOT is set correctly, and mirb is executable. However, under Fish, the script exits non-zero. This error stops chruby from switching the current Ruby, and RUBY_ROOT and other variables remain unchanged.
Description
chruby cannot successfully switch to mruby-3.0.0 under Fish, but seems to work as expected under Bash in spite of raising a Ruby NoMethodError exception when attempting to change rubies. The latter issue was raised upstream with chruby.
Steps To Reproduce
Steps to reproduce the bug:
ruby-install mruby-3.0.0
exec fish --login
, which is required for chruby to pick up the newly installed Rubychruby mruby
orchruby mruby-3.0.0
chruby
, which shows that the selected Ruby hasn't changedExpected Behavior
chruby-fish should not halt execution or report a different exit status than chruby itself. If the Ruby exception is not a show-stopper, then chruby-fish should not halt execution when the Bash version of chruby continues, and should change to the requested Ruby under the same circumstances that the Bash version of chruby does.
Actual Behavior
My default Ruby is currently set to Ruby 3.1.2.
ruby-install mruby-3.0.0
succeeds without error. Under Bash, the following error still occurs:but the current Ruby is changed to mruby-3.0.0, RUBY_ROOT is set correctly, and mirb is executable. However, under Fish, the script exits non-zero. This error stops chruby from switching the current Ruby, and RUBY_ROOT and other variables remain unchanged.
The text was updated successfully, but these errors were encountered: