rake icon indicating copy to clipboard operation
rake copied to clipboard

Stack Level Too Deep in 10.4.2 Rake.application.run

Open coteyr opened this issue 10 years ago • 2 comments

I use Cruise control an was notified of failing builds on the latest update to two of my projects. The problem was a call to

bundle exec rake -v --nosearch --trace -e "Rake.application.run"

That call returned

rake aborted!
rake aborted!

So I dug a bit deeper and found that the real issue is probably:

bundle exec rake -v --nosearch --trace -e "handle_options"

rake aborted!
SystemStackError: stack level too deep

The stack level error "goes away" when using 10.3.2

coteyr avatar Apr 14 '15 02:04 coteyr

This would seem to be related to 95326988452d4e40a7cca23107aefcf5751ffa29 and the like.

coteyr avatar Apr 14 '15 02:04 coteyr

Currently, minimally:

    $ ls | wc -l
    0
    $ rake --version
    rake, version 11.2.2
    $ rake -e "handle_options"
    rake aborted!
    SystemStackError: stack level too deep

MarkDBlackwell avatar Jul 24 '16 16:07 MarkDBlackwell