I'm trying to build an engine http://github.com/radar/forem/tree/broken using RSpec and it gives a "Stack level too deep" on an undefined method when I run bundle exec rspec spec/integration. This is because the forum_path method is undefined, but it also happens with any other undefined method.
bundle exec rspec spec/integration
The problem is that you get a stack trace like this:
As you can see here, it's in an infinite loop, causing the stack level too deep error. I'm interested in any insight that can be offered on this.
This was happening at one point and I fixed it:
I'm surprised a similar thing is happening again. I'll try to take a look when I get a chance. To repro, should I just clone your repo, checkout the broken branch, bundle install and run bundle exec rspec spec/integration?
Thank you for the quick response Myron,
Yes, just clone, checkout, bundle and exec will get you to the same stage I'm at.
I've found that if you comment out your include RSpec::Matchers line from your integration example group module, it fixes the problem.
There's a deeper problem here (including RSpec::Matchers should not have that effect), but I haven't been able to get to the root cause of it yet.
Let's keep this open for now as I continue to investigate it.
Oh neat! Thanks Myron, and good luck finding the root cause.
Prevent SystemStackError on 1.9 when users include RSpec::Matchers in an example group.
Closed by 80e5300.
Prevent SystemStackError on 1.9 when users include RSpec::Matchers in…
… an example group.