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
{{ message }}
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.
Currently there is a problem with print_r in ExceptionHandler formatter, if argument is an object and not simple POCO / DTO but one that contains links to other objects and so on, it becomes very not trivial to dump exception message.
For example, with DoctrineModule, DoctrineORMModule configured in application if i make test exception throw in onBootstrap of module throw new Exception('Evil exception occured'); then the only argument of first trace will be MvcEvent but since it contains information about a lot of in application my memory limit is not enough to log exception, even 512 Mb not enough to log exception.
Possible solution:
would be greate to introduce to ExceptionHandler attribute like traceArgumentLevel that will dump object only to needed level as Doctrine2Debug::dump does.
Currently there is a problem with
print_r
inExceptionHandler
formatter, if argument is an object and not simple POCO / DTO but one that contains links to other objects and so on, it becomes very not trivial to dump exception message.For example, with
DoctrineModule
,DoctrineORMModule
configured in application if i make test exception throw inonBootstrap
of modulethrow new Exception('Evil exception occured');
then the only argument of first trace will beMvcEvent
but since it contains information about a lot of in application my memory limit is not enough to log exception, even 512 Mb not enough to log exception.Possible solution:
would be greate to introduce to
ExceptionHandler
attribute liketraceArgumentLevel
that will dump object only to needed level asDoctrine2
Debug::dump
does.@Maks3w what your thoughs on this one?
The text was updated successfully, but these errors were encountered: