StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Debugging a <code>stack level too deep</code> error message in a <code>rails app</code> isn't easy, since the error could be because of a variety of reasons, and the error message isn't too helpful. </p> <p>Some of the reasons leading to a <code>stack level too deep error</code>:</p> <ol> <li>Inconsistency in the <a href="https://stackoverflow.com/a/2188007/429758">gems & plugins and any other dependencies</a> of the application. </li> <li><a href="http://www.ruby-forum.com/topic/51430" rel="nofollow noreferrer">Code syntax error</a></li> <li>Inconsistency caused by <a href="http://t3h-butter-pecan.blogspot.in/2012/07/my-first-stack-level-too-deep-error-yay.html" rel="nofollow noreferrer">applying db migrations erroneously</a>. </li> </ol> <p>If the error was happening on system boot up, then this tip would be very useful: <a href="http://www.datatravels.com/technotes/2012/07/11/awesome-debugging-for-rails-boot-stacklevel-too-de/" rel="nofollow noreferrer">http://www.datatravels.com/technotes/2012/07/11/awesome-debugging-for-rails-boot-stacklevel-too-de/</a></p> <p>From the description, it looks like the app works fine for a while, and then starts crashing - so the above boot up case might not apply. </p> <p>One way to go about figuring out the problem would to isolate the specific <code>line/block of code</code> that's causing the error by using <a href="https://stackoverflow.com/a/8405963/429758">printf debugging</a></p> <p>Also, it might be worthwhile rolling back the changes and getting the system back to working state, and then put back the changes incrementally to isolate the root cause. </p> <p>It is quite likely the <code>bundle update</code> did trigger the error in this case; so would be a good idea to check the newly added dependencies and see if they could be the culprit. </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload