go-redis/redis · error
redis: empty push notification array length
Error message
redis: empty push notification array length
What it means
Error "redis: empty push notification array length" thrown in go-redis/redis.
Source
Thrown at internal/proto/reader.go:208
if buf[0] != RespPush {
return "", false, fmt.Errorf("redis: can't parse push notification: %q", buf)
}
// Skip the array length line ">N\r\n".
const arrayLenStart = 1 // first byte after the '>' marker
pos, ok, err := skipDigitsThenCRLF(buf, arrayLenStart)
if err != nil {
return "", false, fmt.Errorf("redis: can't parse push notification: %w", err)
}
if !ok {
return "", false, nil
}
// Reject ">\r\n": RESP requires at least one digit for the array length.
// Without this check the empty length looks like a valid prefix and the
// caller would block fetching more bytes for a frame that is already
// malformed.
if pos-2 == arrayLenStart {
return "", false, fmt.Errorf("redis: empty push notification array length")
}
// First element type byte: '$' (bulk) or '+' (simple-string).
if pos >= len(buf) {
return "", false, nil
}
typeOfName := buf[pos]
if typeOfName != RespString && typeOfName != RespStatus {
return "", false, fmt.Errorf("redis: can't parse push notification name: %q", buf[pos:])
}
pos++
if typeOfName == RespString {
// Read "$M\r\n" then the M-byte name.
lenStart := pos
next, ok, err := skipDigitsThenCRLF(buf, pos)
if err != nil {
return "", false, fmt.Errorf("redis: can't parse push notification name length: %w", err)View on GitHub (pinned to 36d97525cd)
Solutions
- Treat as a protocol violation from the server or proxy; reconnect and re-handshake
- Verify RESP3 support of the peer
When it happens
Trigger: Thrown at internal/proto/reader.go:208 when the library encounters an invalid state.
Common situations: Fail the connection on malformed push frames so the pool replaces it.
AI-assisted analysis of go-redis/redis@36d97525cd (2026-08-06).
Data as JSON: /data/errors/a179b7041cd61d0b.json.
Report an issue: GitHub.