Function TestMessageLoopIdleTimeoutClosesConnection

server/conn_idle_test.go:19–51

TestMessageLoopIdleTimeoutClosesConnection proves the mechanism the control-plane idle default relies on: with IdleTimeout configured, a connection that sends nothing hits the read deadline and the message loop returns nil (a clean close), which in the CP triggers DestroySession → worker back to hot

(t *testing.T)

	QueryExecutor
	entered chan struct{}
	release chan struct{}
}

type blockAfterFirstRead struct {
	first             []byte
	firstDelivered    bool
	secondReadStarted chan struct{}
	releaseSecondRead chan struct{}
	secondReadOnce    sync.Once
}

func (r *blockAfterFirstRead) Read(p []byte) (int, error) {
	if !r.firstDelivered {
		r.firstDelivered = true
		return copy(p, r.first), nil
	}
	r.secondReadOnce.Do(func() { close(r.secondReadStarted) })
	<-r.releaseSecondRead
	return 0, io.EOF
}

func (e *blockingDrainExecutor) LastProfilingOutput() string { return "" }

func (e *blockingDrainExecutor) ExecContext(ctx context.Context, _ string, _ ...any) (ExecResult, error) {
	close(e.entered)
	select {
	case <-e.release:
		return nil, nil
	case <-ctx.Done():
		return nil, ctx.Err()
	}
}

// TestMessageLoopIdleTimeoutClosesConnection proves the mechanism the
// control-plane idle default relies on: with IdleTimeout configured, a
// connection that sends nothing hits the read deadline and the message loop