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
I see that this bug was described in rspec-rails #1693 over four years ago, but I'm still seeing it in the most recent minor versions of Ruby and RSpec (2.7 / 3.9).
When executing irb -r <module>, if the given module is either a) RSpec or b) a script that requires RSpec in turn, then the following warning will be printed to the console:
irb: warn: can't alias context from irb_context.
Note that calling require 'rspec' from within irb does not produce the warning:
Subject of the issue
I see that this bug was described in rspec-rails #1693 over four years ago, but I'm still seeing it in the most recent minor versions of Ruby and RSpec (2.7 / 3.9).
When executing
irb -r <module>
, if the given module is either a) RSpec or b) a script that requires RSpec in turn, then the following warning will be printed to the console:Note that calling
require 'rspec'
from withinirb
does not produce the warning:Your environment
Steps to reproduce
Expected behavior
IRB console should be invoked without warning; i.e.:
Actual behavior
The text was updated successfully, but these errors were encountered: