go-redis/redis · error

redis: can't parse int reply: %.100q

Error message

redis: can't parse int reply: %.100q

What it means

Error "redis: can't parse int reply: %.100q" thrown in go-redis/redis.

Source

Thrown at internal/proto/reader.go:516

	case RespInt, RespStatus:
		return util.ParseInt(line[1:], 10, 64)
	case RespString:
		s, err := r.readStringReply(line)
		if err != nil {
			return 0, err
		}
		return util.ParseInt([]byte(s), 10, 64)
	case RespBigInt:
		b, err := r.readBigInt(line)
		if err != nil {
			return 0, err
		}
		if !b.IsInt64() {
			return 0, fmt.Errorf("bigInt(%s) value out of range", b.String())
		}
		return b.Int64(), nil
	}
	return 0, fmt.Errorf("redis: can't parse int reply: %.100q", line)
}

func (r *Reader) ReadUint() (uint64, error) {
	line, err := r.ReadLine()
	if err != nil {
		return 0, err
	}
	switch line[0] {
	case RespInt, RespStatus:
		return util.ParseUint(line[1:], 10, 64)
	case RespString:
		s, err := r.readStringReply(line)
		if err != nil {
			return 0, err
		}
		return util.ParseUint([]byte(s), 10, 64)
	case RespBigInt:
		b, err := r.readBigInt(line)

View on GitHub (pinned to 36d97525cd)

Solutions

1. Check the truncated reply text in the error; the int field is malformed
2. Reconnect if the stream is desynchronized

When it happens

Trigger: Thrown at internal/proto/reader.go:516 when the library encounters an invalid state.

Common situations: Treat integer parse failures as fatal for the connection.

AI-assisted analysis of go-redis/redis@36d97525cd (2026-08-06). Data as JSON: /data/errors/ae99bf7d5ebb5cef.json. Report an issue: GitHub.