Inconsistent behavior in MULTI + ZRANGE

[kukicola]

Describe the bug
When using ZRANGE command within MULTI using RESP3 protocol, result is different in dragonfly compared to redis.

To Reproduce
Take a look at the following queries (connected to instances with -3 parameter to use RESP3):

Redis:

127.0.0.1:6379> keys *
(empty array)
127.0.0.1:6379> ZADD test 500 "value"
(integer) 1
127.0.0.1:6379> ZRANGE test 0 500 WITHSCORES
1) 1) "value"
   2) (double) 500
127.0.0.1:6379> MULTI
OK
127.0.0.1:6379(TX)> ZRANGE test 0 500 WITHSCORES
QUEUED
127.0.0.1:6379(TX)> EXEC
1) 1) 1) "value"
      2) (double) 500

Dragonfly:

127.0.0.1:6380> keys *
(empty array)
127.0.0.1:6380> ZADD test 500 "value"
(integer) 1
127.0.0.1:6380> ZRANGE test 0 500 WITHSCORES
1) 1) "value"
  2) (double) 500
127.0.0.1:6380> MULTI
OK
127.0.0.1:6380(TX)> ZRANGE test 0 500 WITHSCORES
QUEUED
127.0.0.1:6380(TX)> EXEC
1) 1) "value"
  2) (double) 500

Pay attention to nesting in the last response - it's deeper in Redis.

Expected behavior
Dragonfly should return same result as Redis.

Environment (please complete the following information):

• OS: macOS 15.1.1
• Kernel: Darwin Kernel Version 24.1.0
• Containerized?: Docker
• Dragonfly Version: latest docker image - 1.26.0

Reproducible Code Snippet
Just follow the commands provided above

[adiholden]

Thank you @kukicola for reporting this