-
-
Notifications
You must be signed in to change notification settings - Fork 482
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
stack level too deep (SystemStackError)
after upgrading from 4.6.1 to 4.6.2
#1520
Comments
👍 Similar problem on my project. |
Thanks for raising the issue to also let other users add reaction to it 👍 I just checked a few similar gems that have
And So I think it's relatively safe to move from method aliasing to |
@knapo thanks again for the reporting and PR. I've released |
Great, thx a lot too! |
Describe the bug
Per 4dc603b#commitcomment-54080150
4.6.2
extendsRake::Task
with aliasingexecute
method. Unfortunately this causesstack level too deep (SystemStackError)
, whenRake::Task#execute
is overridden using#prepend
To Reproduce
Create a
Rakefile
:Run
rake test
Expected behavior
rake test
should not causeSystemStackError
Actual behavior
rake test
ends withSystemStackError
Environment
The text was updated successfully, but these errors were encountered: