Rueian

That makes sense. Then we have two choices: 1. Since `rayv1.Failed` has gone in v1.2, we don't bring it back: ```go if reconcileErr != nil { // do nothing }...

If we opt for the latter option, it implies a return to the v1.1 behavior. In this case, the `.State` can transition between Ready and Failed states, whereas in v1.2,...

Hi all, I just sent a [PR](https://github.com/ray-project/kuberay/pull/2622/) for the first approach [I mentioned](https://github.com/ray-project/kuberay/issues/2357#issuecomment-2521301187) which leaves the .State untouched and sets the error message to the .Reason field. Please take a...

Hi @fabiomargarido, You are right. Currently, the helper will simplify pipeline GETs to the cluster client. I think it is a good idea to group them into multiple MGETs. Would...

Hi @fabiomargarido, Thanks for bringing up the old commit. Previous to the commit, we did `parallelMGet` which sent `MGET` for each slot parallelly using multiple `DoMulti`, but that was too...

I want to say it makes sense too but I think multiple slots in one MGET is forbidden by redis server.

Hi @UncleVic, I am wondering if you can just release the lock later: ```go ctx, cancel, err := locker.WithContext(context.Background(), "mylock") // use a new context. if err != nil {...

> If I have a few lockers for different gorutins, can I use a single instance of rueidis.Client for those lockers? The best way to do that is preparing a...

> What is different, except a mutex? It returns the shared `client` directly if the client has been created.

@UncleVic do you have any questions?