fix(resp): correct CLIENT REPLY SKIP typo in command kind detection

s/SKIPP/SKIP in the byte pattern matching of `CommandKind::from`.
The extra 'P' prevented `CLIENT REPLY SKIP` from being recognized, so `is_reply_on` was never set to false and the handler incorrectly expected responses for skipped commands.

Author: mcatanzariti

src/resp/command.rs

@@ -128,7 +128,7 @@ impl<'a> From<&'a Command> for CommandKind {
             b"CLIENT" => match (command.get_arg(0).as_deref(), command.get_arg(1).as_deref()) {
                 (Some(b"REPLY"), Some(b"ON")) => CommandKind::ClientReply(ClientReplyMode::On),
                 (Some(b"REPLY"), Some(b"OFF")) => CommandKind::ClientReply(ClientReplyMode::Off),
-                (Some(b"REPLY"), Some(b"SKIPP")) => CommandKind::ClientReply(ClientReplyMode::Skip),
+                (Some(b"REPLY"), Some(b"SKIP")) => CommandKind::ClientReply(ClientReplyMode::Skip),
                 _ => CommandKind::Other,
             },
             b"RESET" => CommandKind::Reset,

src/tests/connection_commands.rs

@@ -201,6 +201,22 @@ async fn client_reply() -> Result<()> {
     Ok(())
 }
 
+#[cfg_attr(feature = "tokio-runtime", tokio::test)]
+#[cfg_attr(feature = "async-std-runtime", async_std::test)]
+#[serial]
+async fn client_reply_skip() -> Result<()> {
+    let client = get_test_client().await?;
+    client.flushdb(FlushingMode::Sync).await?;
+
+    client.client_reply(ClientReplyMode::Skip).forget()?;
+    client.set("skip_key", "skip_value").forget()?;
+    client.client_reply(ClientReplyMode::On).await?;
+    let value: String = client.get("skip_key").await?;
+    assert_eq!("skip_value", value);
+
+    Ok(())
+}
+
 #[cfg_attr(feature = "tokio-runtime", tokio::test)]
 #[cfg_attr(feature = "async-std-runtime", async_std::test)]
 #[serial]