This is encoded as *-1\r\n or $-1\r\n. When we encounter this, we currently fail with error::not_a_number. I think we could support this to soften the RESP3 requirement (I'd say this is the only RESP2 feature we don't support).
For the record, I've encountered this with SENTINEL, as it sends a NULL array if you forget to upgrade the connection to RESP3 with HELLO.
This is encoded as
*-1\r\nor$-1\r\n. When we encounter this, we currently fail witherror::not_a_number. I think we could support this to soften the RESP3 requirement (I'd say this is the only RESP2 feature we don't support).For the record, I've encountered this with SENTINEL, as it sends a NULL array if you forget to upgrade the connection to RESP3 with HELLO.