Madelyn Olson

> I think it will be great if we could team up with the [GLIDE](https://github.com/aws/glide-for-redis) maintainers and explore the opportunity of making GLIDE a native Valkey client. I think GLIDE's...

> We can make a separate interop testing repo. It is about I think it should be this repo, I don't think we want to start introducing tests elsewhere for...

@lipzhu I noticed there wasn't a test, we should at least add one for that.

Yeah, the code changed quite a bit between 7.2 and unstable, and we were trying to be very judicious about the backport. I don't think we thought about this one....

So I guess we are saying that for 7.2, it will stay compatible with Redis, then when release Valkey 8.0 it will reflect the valkey version?

Ok, so maybe something that would be make me "happyish": ``` CSCAN [SLOT X] [MATCH pattern] [COUNT count] [TYPE type] ``` Which just scans the given slot if it's provided....

If SLOT is provided, it would only be valid for the SLOT specified. If it's omitted, it would do a scan across all slots in the cluster.

> I wonder whether a cursor might become "accidentally" usable between regular SCAN, CSAN, and CSCAN+slot calls, simply because its computed in the same way for each call. That's possible,...

> if the client isn't aware of slot 2 moving from A to B Then it'll get a MOVED message and try again. This is the normal behavior for misunderstanding...

> How do we plan to make these commands available via scripts/transactions? I would imagine CSCAN will probably be non-script, but SCAN with specific slot will be available right? Why...