Petr Levtonov comments

Results 47 comments of


                                            Petr Levtonov

Question regarding loadInto()

Any input how we can proceed with this issue? Can we help with a pull request on our own?

Encountering the same issue now. Laravel test runs: ```php $x = Cache::store()->getStore(); $y = $x->putMany([ 'a' => new Entity(), 'b' => new Entity(), 'c' => new Entity(), ], 60); dump($x->get('b'));...

redis cluster multi bug

We see different kind of errors depending also on whether we have slot caching enabled.

PHP Redis - Cluster Connection timeout.

> RedisClusterException with message 'Timed out attempting to find data in the correct node!' Related issue here. Can it be that if server timeout is set (closes idle connections), the...

ErrorException: Caught ErrorException (HTTP/1.0 500 Internal Server Error): fwrite(): write of X bytes failed with errno=32 Broken pipe

> We stream it via stout and stderr which then goes out to Datadog. Same issue and same use case.

Question regarding loadInto()

Well we have overwritten the class and so far it works fine and as expected for over a year now. I will submit the proposal soon.

Problems on Symfony 5.0

Check https://github.com/TheLevti/phpfork. Its a fork of this repo where I try to keep it up to date. Its still work in progress and hopefully I can provide a pull request...

Keep alive support

Would be amazing to get this support out. I suspect I have such a case where sometimes the connection is just gone and I am stuck listening forever.

Issue with Logging to stdout in Laravel 10.21 using Monolog v3 EXCEPTION#Cannot log request: fwrite(): Write of 378 bytes failed with errno=32 Broken pipe

Hello! Encountering the same issue on many of my projects as I log to stdout with json formatter.

Issue with Logging to stdout in Laravel 10.21 using Monolog v3 EXCEPTION#Cannot log request: fwrite(): Write of 378 bytes failed with errno=32 Broken pipe

As already mentioned, only happens in fpm context, not for long running processes/cronjobs. ~I will check if we can run the patch to see if it resolves the issue.~ Going...