Madelyn Olson

We're still investigating what makes the most sense. For now there is not plan to proactively fork the other clients. We are working on getting clients to explicitly indicate what...

> Can Redict and Valkey make any agreement about a such libs? Also, as I understand it still controlled by Redis Lab and they can provide protection to avoid use...

@roshkhatri There is a memory sanitization error. Looks like we're leaking some memory now.

> had tried the original client approach first. The change becomes a bit complex due to maintaining the start index of the clientReplyBlock as well as the start index within...

> However, after we finish adding the command reply to reply list and we want to add the length of the reply we optimize using setDeferredReply https://github.com/valkey-io/valkey/blob/unstable/src/networking.c#L762, which makes it...

> Have we considered using a dedicated client like the fake AOF client? That would still you the "clean" slate but reduce the work associated with creating/deleting the client. Not...

I think we can close this now. I see that there are now followup issues for other distribution containers. Help is definitely appreciated to get all of those setup. Please...

> The problem addressed in this PR (asymmetric cluster membership) can happen with SYNC MEET as well due to link failures. So, it is worth solving it. The handshake nodes...

> Awesome material for our next release which will be full of cluster improvements. Is it worth mentioning in release notes? I would also be inclined to backport it.

I was pretty strongly against this command because I don't want to add commands that aren't solving a problem. HSCAN without values made more sense, because values can be large,...