Oran Agra

@redis/core-team are we ok to merge this to 8.0, and do we consider that a breaking change? (see my quote above)

we discussed this in a core-team meeting, the decision was to consider this a breaking change to be released in 8.0. we do agree it is worth fixing.

@ClaytonNorthey92 i'm sorry for the delay, i'm currently busy elsewhere and didn't yet get to review or try this PR. It is on my list, hope to get to it...

@redis/redis-committers maybe one of you can find time to review this.

> (Sorry @oranagra for saying that it's ready to merge. I thought it was.) NP, when ready, better ping me on slack (i might miss the notification here)

what's the status here? i would hate all the effort already invested to be lost...

@linzihao1999 thanks. AFAICT i think the current version looks good. i think it was me that suggested that all the headache with this command comes from the fact `end` is...

we discussed this in a core-team meeting, we do agree it is worth fixing. (as a breaking change to be released in 8.0). @linzihao1999 please ack on my previous message...

is the behavior change only when `end < -strlen`? or like i wrote above when `start

@panjf2000 thank you for this PR. > By using `epoll_pwait2()`, we can resolve the problem in #8764 faultlessly, once and for all. what do you mean? i might not recall...