PHP Xdebug has detected a possible infinite loop when logged in with non-admin user about framework

[n-peugnet]

Can't reproduce, what are your tag restrictions like? it seems like the problem may at the tag access check level.

I had one restriction by tag, for testing purpose (just clicked once to add the tag without editing anything). I removed it but the issue persisted.

I just tried to set Flarum's own Debug mode to false and the issue did not happen. So I guess it only happens with both Xdebug and Flarum's debug mode enabled. This is still an issue, as when doing local development, it is not rare to enable both at the same time.

[n-peugnet]

@n-peugnet how much is your nesting level for php configured at?

I guess you are talking about the xdebug.max_nesting_level setting. I didn't set it myself so I imagine 200 is the default value on Debian. I tried to increase it with no luck. It seems 200 is the max I can specify.

php -dxdebug.max_nesting_level=500 -S localhost:8080 -t public

However, using lower values than 200 works, it indeed affects this behaviour by stopping the execution sooner. Maybe I should report this problem to Xdebug instead.

Anyways, this is not that much of a problem for me anymore as I mostly use the debug mode and not that much the develop one. Feel free to close this issue whenever you want.

[SychO9]

Can't reproduce, what are your tag restrictions like? it seems like the problem may at the tag access check level.

[n-peugnet]

Small update: this seems to happen only with Xdebug's default develop mode¹². When I set the mode to debug using either of these methods the problem does not show up:

XDEBUG_MODE=debug php -S localhost:8080 -t public
php -d xdebug.mode=debug -S localhost:8080 -t public

Footnotes

1. https://xdebug.org/docs/all_settings#mode ↩

2. https://xdebug.org/docs/develop ↩

[luceos]

@n-peugnet how much is your nesting level for php configured at?

[linc]

For what it's worth, I also ran into this with xdebug.mode=develop and switching to debug worked. PHP 8.1 on a forum I've been running import tests on and hadn't loaded in a few months, so who knows what triggered it. It was specifically being logged in already as a non-admin, I think.