I have tested this item ✅ successfully on 5a02415

Tested successfully in Beta7-dev of 19 January using PHP 8.0.1.

I have tested this item ✅ successfully on 5a02415

RTC

I get error handling is hard for some of y’all, but this is just a garbage hack that makes debugging errors next to impossible, might as well just print “LOLZ IT BROKE”.

Don’t merge this mess, do it right. Overload the exception handling of the console application’s execute method and tweak it to do whatever you want. There is a reason exception handling is done inside the application and not left to be handled in front controllers or entry point files, you have the entire app framework at your disposal inside the app (which, BTW, with the default application workflow means someone can add meaningful exception logging and dispatch events that can be subscribed to which allows add-on integrations to do something meaningful with errors; shocking, I know, who woulda thought you could allow add-one to do useful things in an application intended to be extended with add-one) whereas with this patch you have no way of debugging because the entire exception is swallowed.

Also, generally if there’s an uncaught exception in the exception handling layer, you typically want a noisy output in the CLI integration, as that generally means something is catastrophically broken and needs attention 10 minutes ago. This patch silences that with zero gain.

@mtbraoblkler if you are fully right then simply submit a PR....

@alikon I think you didnt realise who is behind the fake account

@brianteeman no i don't know... but doesn't matter ?

Unfortunately @mtbraoblkler is correct. This should be overloaded in our ConsoleApplication. I think https://github.com/joomla-framework/console/blob/master/src/Application.php#L914-L943 is the method you want to duplicate in the CMS ConsoleApplication class