Maximum function nesting level of '100' reached

I've been having trouble with Laravel 5.2. Somehow on rare occasions I've got bla bla bla something maximum function nesting level 100 reached. Thinking that might be cause of of doing something wrong, ideally I love to nest templates and recycle them as much as possible. This applies to model, controller logic too. So naturally I was thinking that is causing that problem. But fixing was impossible. I've started hardcoding them instead making things dynamic until I felt really shitty. So investigating that issue guided here https://laracasts.com/discuss/channels/general-discussion/l5-maximum-function-nesting-level-of-100-reached-aborting?page=3

Which is turns out x-debug just doesn't want to nest functions till 100 level by default. Which is actually good to figure which things going over the limit. But L5 just likes to go deeper than that. So end solution was increase xdebug nesting like this.

xdebug.max_nesting_level = 112

Not an actual fix or something rather just increasing limit like increasing memory. So that's that I've never had this kind of problem with L4 though. So keep in mind when you deploying this increase this limit on production as well.

Comments

Popular posts from this blog

Set up RAID on Dell Poweredge 2850

How to implement Blueimp with Laravel 5

HackUB (Hackathon Ulaanbaatar) - Organizing event