Closed convenient closed 8 years ago
Please search through existing issues AFAIK this has been reported earlier. Thanks :)
I saw similar errors like https://github.com/netz98/n98-magerun/issues/642, but will investigate more thoroughly later
Having same issue as @convenient and found that magento apps with custom error handlers cause the script to die()
can cause this issue. The dependency Symfony\Console\Helper\HelperSet.php
includes a mechanism for deprecation which uses @trigger_error
and whilst this deprecation will be ignored if the error handler also suppresses it, if not then magerun will die.
The deprecation mechanism was introduced in the Symfony\Console
at the 2.7 branch which a dependency of magerun from 1.97.6
This is not a magerun issue but magerun is not compatible with Symfony\Console
>= 3.x when the deprecation is removed.
Boy is my face red.
The custom error handler for the magento project was overly aggressive, making @
errors noisy again. Pretty much like xdebug.scream
. This was with the intention of making the developers write better code with proper error handling.
When the suppressed error was triggered the custom error handler then did exactly what we wanted, and blew up over the suppressed error.
Closing as it was totally an internal issue.
The issue
Project composer.lock
Sadly the project is closed source.
The only thing that pops up the the projects
composer.lock
when I search for symfony is: