You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running client info inside a MULTI transaction, the response QUEUED is incorrectly concatenated with the prompt, making it hard to read. This appears to be an output formatting issue in valkey-cli.
127.0.0.1:6379> multi
OK
127.0.0.1:6379(TX)> client info
QUEUED127.0.0.1:6379(TX)>
To reproduce
127.0.0.1:6379> multi
127.0.0.1:6379(TX)> client info
Expected behavior
The expected output should properly format the QUEUED response, ensuring correct spacing and line breaks:
QUEUED
127.0.0.1:6379(TX)>
Additional information
Other commands (set, get) inside a transaction do not exhibit this behavior. The response type is REDIS_REPLY_VERB for client info.
The text was updated successfully, but these errors were encountered:
Describe the bug
When running client info inside a
MULTI
transaction, the responseQUEUED
is incorrectly concatenated with the prompt, making it hard to read. This appears to be an output formatting issue invalkey-cli
.To reproduce
Expected behavior
The expected output should properly format the QUEUED response, ensuring correct spacing and line breaks:
QUEUED
127.0.0.1:6379(TX)>
Additional information
Other commands (set, get) inside a transaction do not exhibit this behavior. The response type is
REDIS_REPLY_VERB
forclient info
.The text was updated successfully, but these errors were encountered: