From 04dfda8a0edb5bf7bd3d7a265b5928a2ec852d40 Mon Sep 17 00:00:00 2001 From: Spike Curtis Date: Wed, 3 Sep 2025 13:42:02 +0400 Subject: [PATCH] fix: change enqueue error to debug log level (#19686) fixes https://github.com/coder/internal/issues/958 Logging was being done at error level, but most likely any errors are from simple races between an update triggered around the same time as a client disconnecting. Debug is fine for these. --- enterprise/tailnet/pgcoord.go | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/enterprise/tailnet/pgcoord.go b/enterprise/tailnet/pgcoord.go index 1283d9f353..32bd896669 100644 --- a/enterprise/tailnet/pgcoord.go +++ b/enterprise/tailnet/pgcoord.go @@ -693,8 +693,9 @@ func (m *mapper) run() { m.logger.Debug(m.ctx, "skipping nil node update") continue } - if err := m.c.Enqueue(update); err != nil && !xerrors.Is(err, context.Canceled) { - m.logger.Error(m.ctx, "failed to enqueue node update", slog.Error(err)) + if err := m.c.Enqueue(update); err != nil { + // lots of reasons this could happen, most usually, the peer has disconnected. + m.logger.Debug(m.ctx, "failed to enqueue node update", slog.Error(err)) } } }