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
I found a warning in production deployment about the zend.assertions usage:
E_WARNING: zend.assertions may be completely enabled or disabled only in php.ini in /var/www/html/vendor/symfony/error-handler/Debug.php:32
#0 ini_set called at [/var/www/html/vendor/symfony/error-handler/Debug.php:32]
#1 Symfony\Component\ErrorHandler\Debug::enable called at [/var/www/html/vendor/dukecity/command-scheduler-bundle/Service/CommandParser.php:78]
#2 Dukecity\CommandSchedulerBundle\Service\CommandParser::getAvailableCommands called at [/var/www/html/vendor/dukecity/command-scheduler-bundle/Service/CommandParser.php:114]
#3 Dukecity\CommandSchedulerBundle\Service\CommandParser::getCommands called at [/var/www/html/vendor/dukecity/command-scheduler-bundle/Form/Type/CommandChoiceType.php:28]
#4 Dukecity\CommandSchedulerBundle\Form\Type\CommandChoiceType::configureOptions called at [/var/www/html/vendor/symfony/form/ResolvedFormType.php:183]
#5 Symfony\Component\Form\ResolvedFormType::getOptionsResolver called at [/var/www/html/vendor/symfony/form/ResolvedFormType.php:100]
#6 Symfony\Component\Form\ResolvedFormType::createBuilder called at [/var/www/html/vendor/symfony/form/FormFactory.php:69]
#7 Symfony\Component\Form\FormFactory::createNamedBuilder called at [/var/www/html/vendor/symfony/form/FormBuilder.php:97]
#8 Symfony\Component\Form\FormBuilder::create called at [/var/www/html/vendor/symfony/form/FormBuilder.php:249]
#9 Symfony\Component\Form\FormBuilder::resolveChildren called at [/var/www/html/vendor/symfony/form/FormBuilder.php:199]
#10 Symfony\Component\Form\FormBuilder::getForm called at [/var/www/html/vendor/symfony/form/FormFactory.php:31]
#11 Symfony\Component\Form\FormFactory::create called at [/var/www/html/vendor/symfony/framework-bundle/Controller/AbstractController.php:366]
#12 Symfony\Bundle\FrameworkBundle\Controller\AbstractController::createForm called at [/var/www/html/vendor/dukecity/command-scheduler-bundle/Controller/DetailController.php:29]
#13 Dukecity\CommandSchedulerBundle\Controller\DetailController::edit called at [/var/www/html/vendor/symfony/http-kernel/HttpKernel.php:163]
#14 Symfony\Component\HttpKernel\HttpKernel::handleRaw called at [/var/www/html/vendor/symfony/http-kernel/HttpKernel.php:75]
#15 Symfony\Component\HttpKernel\HttpKernel::handle called at [/var/www/html/vendor/symfony/http-kernel/Kernel.php:202]
#16 Symfony\Component\HttpKernel\Kernel::handle called at [/var/www/html/vendor/symfony/runtime/Runner/Symfony/HttpKernelRunner.php:35]
#17 Symfony\Component\Runtime\Runner\Symfony\HttpKernelRunner::run called at [/var/www/html/vendor/autoload_runtime.php:35]
#18 require_once called at [/var/www/html/public/index.php:5]
Does Debug::enable() should be used in production?
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Package version: 5.0.10
I found a warning in production deployment about the
zend.assertions
usage:E_WARNING: zend.assertions may be completely enabled or disabled only in php.ini in /var/www/html/vendor/symfony/error-handler/Debug.php:32
Does
Debug::enable()
should be used in production?The text was updated successfully, but these errors were encountered: