Closed weierophinney closed 3 years ago
bump
Originally posted by @Ragazzo at https://github.com/zendframework/zend-log/issues/16#issuecomment-165363828
This package is considered feature-complete, and is now in security-only maintenance mode, following a decision by the Technical Steering Committee. If you have a security issue, please follow our security reporting guidelines. If you wish to take on the role of maintainer, please nominate yourself
If you are looking for an actively maintained package alternative, we recommend:
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?
Originally posted by @Ragazzo at https://github.com/zendframework/zend-log/issues/16