What causes "can't call SetWriteDeadline for ConnWithTimeouts" in vitessio/vitess?

Use the underlying plain net.Conn for deadline-based consumers.

can't call SetWriteDeadline for ConnWithTimeouts

Error message

can't call SetWriteDeadline for ConnWithTimeouts

What it means

SetWriteDeadline on ConnWithTimeouts panics by design: write timeouts are enforced inside Write using the configured write timeout, so per-call deadline APIs are unsupported. This stub turns a semantic misuse into an immediate, loud failure.

Source

Thrown at go/netutil/conn.go:71

	if err := c.Conn.SetWriteDeadline(time.Now().Add(c.writeTimeout)); err != nil {
		return 0, err
	}
	return c.Conn.Write(b)
}

// SetDeadline implements the Conn SetDeadline method.
func (c ConnWithTimeouts) SetDeadline(t time.Time) error {
	panic("can't call SetDeadline for ConnWithTimeouts")
}

// SetReadDeadline implements the Conn SetReadDeadline method.
func (c ConnWithTimeouts) SetReadDeadline(t time.Time) error {
	panic("can't call SetReadDeadline for ConnWithTimeouts")
}

// SetWriteDeadline implements the Conn SetWriteDeadline method.
func (c ConnWithTimeouts) SetWriteDeadline(t time.Time) error {
	panic("can't call SetWriteDeadline for ConnWithTimeouts")
}

View on GitHub (pinned to 01a25a7d17)

Solutions

Use the underlying plain net.Conn for deadline-based consumers.
Tune the write timeout supplied to WithTimeouts to cover slow-writer cases.
Refactor to a deadline-based conn (drop WithTimeouts) if deadlines are the actual requirement.

Example fix

// before
conn.SetWriteDeadline(time.Now().Add(10 * time.Second)) // panics
// after
// configure once:
conn := netutil.ConnWithTimeouts{Conn: raw, WriteTimeout: 10 * time.Second}

Defensive patterns

Strategy: type-guard

Validate before calling

if _, isTimeouts := conn.(netutil.ConnWithTimeouts); isTimeouts {
    return errors.New("use per-call timeouts, not SetWriteDeadline")
}

Type guard

func isConnWithTimeouts(c net.Conn) bool {
    _, ok := c.(netutil.ConnWithTimeouts)
    return ok
}

Try / catch

defer func() { if r := recover(); r != nil { err = fmt.Errorf("SetWriteDeadline unsupported: %v", r) } }()

Prevention

Encode write timeout in WriteTimeout at conn creation.
Avoid frameworks that refresh write deadlines per request.
Prefer plain conns when deadline semantics are a hard requirement.

When it happens

Trigger: Calling SetWriteDeadline directly, or giving the conn to libraries that set write deadlines (TLS record writing, HTTP response writing, chunked proxy relays).

Common situations: Writing proxy/server code that periodically refreshes write deadlines for slow clients; integrating with frameworks assuming standard net.Conn deadline semantics.

Understand the failure class

Timeouts: ETIMEDOUT, deadlines, and hung requests — what actually expires when a request times out.

Related errors

AI-assisted analysis of vitessio/vitess@01a25a7d17 (2026-09-01). Data as JSON: /api/errors/b8d8d11ba9d7debc. Report an issue: GitHub.