Monkey

any news?

I discovered this issue during an unexpected power outage. The issue can also be reproduced using kill -9, but it's not 100% reproducible. It's more likely to occur when inserting...

Any news?

I only set the RDB strategy (AOF is disabled), and during one test, the issue was reproduced. It seems like there might be data corruption? I'm not sure if shutting...

Yes, it does indeed have flaws and potential risks.

I don't quite understand what it means. The go-redis connection to redis-cluster is different from a standalone Redis connection. It will use the node address returned by redis-cluster (CLUSTER NODES)....

You should use the `Option.Dialer` property instead, compared to `ConnCheck`, as it can create the network connection you want, as long as it conforms to the `net.conn` interface. `ConnCheck` checks...

/cc @vmihailenco @elena-kolevska @chayim @SoulPancake Are you interested? You can share your opinions. 😊

This is a simple usage example: ```go func TestRedisPlugin(t *testing.T) { client := redis.NewClient(&redis.Options{ Addr: "127.0.0.1:6379", }) ctx := context.Background() client.RegistryPostInitConnPlugin(func(ctx context.Context, conn *redis.Conn) error { conn.ClientSetName(ctx, "test-client") return nil...

We treat them as special API, distinct from regular commands.