go-redis/redis · error

redis: can't parse bigInt reply: %q

Error message

redis: can't parse bigInt reply: %q

What it means

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

Source

Thrown at internal/proto/reader.go:397

	return strconv.ParseFloat(v, 64)
}

func (r *Reader) readBool(line []byte) (bool, error) {
	switch util.BytesToString(line[1:]) {
	case "t":
		return true, nil
	case "f":
		return false, nil
	}
	return false, fmt.Errorf("redis: can't parse bool reply: %q", line)
}

func (r *Reader) readBigInt(line []byte) (*big.Int, error) {
	i := new(big.Int)
	if i, ok := i.SetString(util.BytesToString(line[1:]), 10); ok {
		return i, nil
	}
	return nil, fmt.Errorf("redis: can't parse bigInt reply: %q", line)
}

func (r *Reader) readStringReply(line []byte) (string, error) {
	n, err := replyLen(line)
	if err != nil {
		return "", err
	}

	b := make([]byte, n+2)
	_, err = io.ReadFull(r.rd, b)
	if err != nil {
		return "", err
	}

	return util.BytesToString(b[:n]), nil
}

func (r *Reader) readVerb(line []byte) (string, error) {

View on GitHub (pinned to 36d97525cd)

Solutions

1. Verify the big-number frame content quoted in the error
2. Use RESP2 if the peer cannot produce valid big integers

When it happens

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

Common situations: Fall back to string parsing for big numbers when interop is uncertain.

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