You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you throw an exception (throw new \Exception('Some error...');) in CLI mode the script silently dies without no output to the console. It is only logged in PHP's error log.
That should not be default behaviour I would say.
Btw, this is on Windows. If I run it in my Linux environment it should just fine.
The text was updated successfully, but these errors were encountered:
Anyway - have you checked display_errors in your ini file? Note that the cli will typically be using a different ini file to the one used by your webserver.
php -r "phpinfo();" | grep php.ini to check for which one it's using.
php -d display_errors=on .... to override it anyway.
The framework sets ini_set('display_errors',0); on initialization, so I think it should be handle displaying at least any error message if not QUIET turned on.
When you throw an exception (
throw new \Exception('Some error...');
) in CLI mode the script silently dies without no output to the console. It is only logged in PHP's error log.That should not be default behaviour I would say.
Btw, this is on Windows. If I run it in my Linux environment it should just fine.
The text was updated successfully, but these errors were encountered: