Stack Level Too Deep in 10.4.2 Rake.application.run

Open
#41 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
build-system, cli

Research direction

Reproduce the reported commands with Rake 10.4.2 and compare them with 10.3.2, using the --trace output to identify where handle_options recurses. Confirm that the newer version no longer reports repeated “rake aborted!” messages or SystemStackError for these invocations.

Written by the indexing model from the issue text.

Description

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

Dominant language
Ruby
Stars
2.5k
Forks
649
Avg merge
4m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ruby/rake

All issues in ruby/rake

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.