fix: ignore MaxFlushDelay for blocking commands

[unknowntpo]

We check if one or multi has block command, if true, then there's no need to sleep.

[unknowntpo]

@rueian This test takes too much time, maybe something is wrong.
https://app.circleci.com/pipelines/github/redis/rueidis/1021/workflows/2868a79d-6e02-4b6e-aead-d65fa1c4e01b/jobs/977

[rueian]

@rueian This test takes too much time, maybe something is wrong. https://app.circleci.com/pipelines/github/redis/rueidis/1021/workflows/2868a79d-6e02-4b6e-aead-d65fa1c4e01b/jobs/977

It looks like the DragonflyDB crashed during the test. Now the tests are passed after rerun.

[unknowntpo]

@rueian This test takes too much time, maybe something is wrong. https://app.circleci.com/pipelines/github/redis/rueidis/1021/workflows/2868a79d-6e02-4b6e-aead-d65fa1c4e01b/jobs/977

It looks like the DragonflyDB crashed during the test. Now the tests are passed after rerun.

Thanks for helping!
And BTW, I notice that the test for MaxFlushDelay is weird, it inits a WaitGroup, but didn't use wg.Wait() to wait for it.
What's the purpose of this test?

rueidis/pipe_test.go

Line 765 in f10a1ee

wg := sync.WaitGroup{}

[rueian]

@rueian This test takes too much time, maybe something is wrong. https://app.circleci.com/pipelines/github/redis/rueidis/1021/workflows/2868a79d-6e02-4b6e-aead-d65fa1c4e01b/jobs/977

It looks like the DragonflyDB crashed during the test. Now the tests are passed after rerun.

Thanks for helping! And BTW, I notice that the test for MaxFlushDelay is weird, it inits a WaitGroup, but didn't use wg.Wait() to wait for it. What's the purpose of this test?

rueidis/pipe_test.go

Line 765 in f10a1ee

wg := sync.WaitGroup{}

Yes, the wg is not used and can be removed.

The purpose of that test is just to make sure that the mock.Expect("PING").ReplyString("OK") can be passed.

[unknowntpo]

rueidis/pipe_test.go

Okay, would you like me to send a PR to remove it ?