Forwarded to devs Laravel Toolkit generates Laravel Exception whenever used

[Martin Allen]

Username:

TITLE

Laravel Toolkit generates Laravel Exception whenever used

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Laravel Toolkit, Version 1.4.2-221, AlmaLinux 8.7 (Stone Smilodon)

PROBLEM DESCRIPTION

Whenever an action within the Laravel Toolkit is triggered e.g. deployment, the following Exception is thrown by Laravel

production.ERROR: There are no commands defined in the "plesk-ext-laravel" namespace. {"exception":"[object] (Symfony\Component\Console\Exception\NamespaceNotFoundException(code: 0): There are no commands defined in the "plesk-ext-laravel" namespace. at /var/www/vhosts/***redacted***/application/vendor/symfony/console/Application.php:632)"} []

Instead of simply executing a command in the "plesk-ext-laravel" namespace, the "Laravel Toolkit" should first check if the package is installed.

This causes Laravel Logs to include lots of extra unnecessary exceptions, and automated error logging (e.g. automated error notifications to Slack / Email) are constantly being triggered

STEPS TO REPRODUCE

Setup a Laravel Application that does NOT have the plesk-ext-laravel package installed

Perform an automated deployment, then check the Laravel logs

ACTUAL RESULT

production.ERROR: There are no commands defined in the "plesk-ext-laravel" namespace. {"exception":"[object] (Symfony\Component\Console\Exception\NamespaceNotFoundException(code: 0): There are no commands defined in the "plesk-ext-laravel" namespace. at /var/www/vhosts/***redacted***/application/vendor/symfony/console/Application.php:632)"} []

is added to logs (as Logs can be configured differently in each Laravel application, results may vary depending upon this configuration)

EXPECTED RESULT

No Exceptions to be thrown

ANY ADDITIONAL INFORMATION

See Issue - Latest update on "Laravel Toolkit" causes Errors
for more info

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Peter Debik]

Thank you for reporting. This has been forwarded as ID [PPS-13969] to developers. You can use this ID to point support staff to the case if new questions come up.

 

[Peter Debik]

The bug was already known and has also been fixed here already. The fix will become available in one of the nearest updates. Issue ID [EXTPLESK-4335].