fix(stream): Fix XPENDING serialization issue

[nathanlo-hrt]

Currently XPENDING doesn't properly create and serialize an array of the right length: the response to an XPENDING command is always an array of length 4, regardless of the number of consumer infos it has to send back.

The existing tests pass because they all happened to have exactly one consumer.

[torwig]

Stream test time out after 30 minutes. Maybe there is a block or infinite wait (for example, waiting for a message that is never added).

[torwig]

@nathanlo-hrt Thank you for this catch.

[PragmaTwice]

Stream test time out after 30 minutes. Maybe there is a block or infinite wait (for example, waiting for a message that is never added).

So.. is this another bug of XPENDING? Or we can just change the test case to fix it?

[nathanlo-hrt]

I believe this is a bug in my changes to the test code; I'll put up a fix later today. Thanks for the swift reviews!

[nathanlo-hrt]

Found another issue while testing: Kvrocks currently deviates from Redis' behavior when there are no pending messages. I've added a special case for this and a test to cover the new code.

[torwig]

@nathanlo-hrt Good job! You can run ./x.py format to format the code and make the linter happy.

[torwig]

Error: unit/type/stream/stream_test.go:2170:6: ineffectual assignment to err (ineffassign)
		r, err := rdb.XAck(ctx, streamName, groupName, "0-0").Result()

[torwig]

LGTM with minor comment.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
62.4% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud