Maximilian Schirmer

I've made some adjustments within phpunits config ``` cacheResult ="false" enforceTimeLimit="true" (necessary as I don't have dynamodb AWS keys) ``` And got the following output on W11 + WSL2 (tests...

Same for us since upgrading to 5.3.2. `Can't communicate with any node in the cluster RedisCluster::get(): SSL: Handshake timed out` Note: We're not using SSL for redis cluster connection. We'll...

@yatsukhnenko which we do not. Below laravel config works fine for phpredis 5.3.1, but will break at 5.3.2 due to above error. REDIS_SCHEME is not set by any of our...

Could be, but why should this behaviour differ wether we use phpredis 5.3.1 or 5.3.2 with 100% same codebase? I'm running the same source on 2 different Dockerfiles, one with...

@yatsukhnenko works fine using 5.3.2: ``` $obj_cluster = new RedisCluster(NULL, Array("redis-node-0:6379", "redis-node-1:6379"), 1.5, 1.5, true); $obj_cluster->set("mykey", "new_value"); dd($obj_cluster->get("mykey")); ``` As this also affects @Diamonds0a , who isn't using laravel wrapper...

Very well - may I ask you to point out what - in your opinion - would be the most likely reason for laravel to fail with 5.3.2? Just so...

Laravel was already aware of this issue and will provide a patch today :-) Thanks, both of you!

> Laravel v8.12.0 was released along with a fix. This issue can be closed. OP wasn't mentioning laravel, I've just hijacked this issue as I thought it was phpredis related.

Had the same issue a while ago, logging to stderr instead of stdout solved the issue for us. As log levels are set explicitly anyhow, this does not affect logging...