Monkey

> I ran my new tests from #2433 against this branch, and one is failing: `PubSub canceled context [It] should unblock ReceiveMessage`. That being said, this is still a huge...

```go clientMock.Regexp().ExpectSet(".*", ".*", 1*time.Second).SetVal("regexp set val") set = client.Set(ctx, "rand_key", "rand_value", 1*time.Second) Expect(set.Err()).NotTo(HaveOccurred()) Expect(set.Val()).To(Equal("regexp set val")) ``` After testing, it can work normally.

Thank you for your feedback. go-redis has not been adapted for IPv6. Are you interested in submitting a PR?

I'm not sure where the problem lies. In cluster mode, go-redis perceives all nodes within the cluster through the cluster slots command, using their IP addresses and ports to establish...

Can you print the result of cluster slots? See: https://redis.io/docs/latest/commands/cluster-slots/

I currently do not have more devices to build an IPv6 cluster for testing. I am not sure about the data format of MOVE ADDR. If it looks like MOVE...

redis ipv6 issue https://github.com/redis/redis/issues/6238 It looks like we can make some compatibility adjustments to handle both fd01:abcd::7d03:6379 and [fd01:abcd::7d03]:6379 types of IPv6 addresses properly. @daviddzxy, can you continue?

Moreover, under normal circumstances, go-redis should not encounter MOVE. Before sending a command, go-redis calculates the node for the key and sends the Redis command to that node. This type...

> Should I create another issue for this bug? I plan to make a PR with a fix later today. OK!

It looks like this is an issue introduced by #2688, which seems to affect many APIs. However, go-redis needs to ensure API compatibility. It looks like we'll need to come...