Robust Error Handling

Error Handling

A production key-value store spends a surprising amount of its logic on things that don't work: malformed requests, wrong argument counts, and inconsistent casing from different clients. This lesson hardens your PING/ECHO dispatcher so that later commands (which are far more complex) inherit a validation pattern instead of reinventing it each time.

Case-insensitive commands

Real Redis clients send commands in whatever case is convenient — set, SET, Set are all valid. Your dispatcher should normalize once, at the boundary:

Do this normalization in exactly one place. If you find yourself calling .upper() in multiple handlers, that's a sign the dispatch loop isn't doing its job — the handler should never see anything but the canonical uppercase name.

Argument-count validation

Every command has an arity — a minimum (and sometimes maximum) number of arguments. PING accepts zero or one; more than one is an error. ECHO requires exactly one. The Redis error format for this is standardized:

-ERR wrong number of arguments for '<cmd>' command\r\n

Note that the command name inside the message is lowercased in real Redis error text ('ping', not 'PING') even though matching itself is case-insensitive — check the exact expected casing in your test cases and match it precisely, since these are exact-string tests.

A clean way to encode arity rules as you add more commands:

Call this before invoking the handler, so every command gets the same validation for free.

Empty lines

Interactive stdin sessions (and test harnesses that send trailing newlines) will sometimes hand you a blank line. Treat it as a no-op — skip it silently rather than treating it as an unknown command:

Getting this wrong is a common source of subtle test failures: your program emits an extra -ERR unknown command '' reply that shifts every subsequent expected line out of alignment.

Why this matters beyond PING/ECHO

You're building this validation layer now, on the two simplest commands, so that when you implement SET key value NX EX 10 a few lessons from now, argument checking is a solved, reusable concern — not something tangled into business logic. Keep the three concerns separate: parse the line into tokens, validate arity/shape, then execute the handler.