Refs https://github.com/Seldaek/monolog/pull/474/files
The fix in the previous PR did not take into account that there might be object wrapped resources that would break json_encode, so the best solution would be normalizing those frames again.
@Seldaek Sorry for the inconvenience, but our graylog is still ramming up with those json_encode error messages.
With `React` or `Guzzle`, that register stream wrappers with PHP, the traces are treated as coming from internal functions with no line and file inside the frame. But they almost always contain resources as arguments, on which the `json_encode()` call will choke (probably this should be addressed in json_encode internally, since it is very easy to cast a resource to a string).
I added a test case proving the situation and a pretty basic recursive checker for resources which just casts them as a string into the frame again.
