From 66d2a14e47bef8810c1157e00a891a470d945eb9 Mon Sep 17 00:00:00 2001 From: Trong Huu Nguyen Date: Mon, 11 May 2026 15:28:14 +0200 Subject: [PATCH] fix(handler/error): respect log level parameter in respondError The previous if/else only checked for WarnLevel, causing any other level (e.g. InfoLevel in 24fb9b1) to fall through to Errorf. Use Logf to dispatch on the actual level passed by callers. --- pkg/handler/error.go | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/pkg/handler/error.go b/pkg/handler/error.go index d0d5498..4bc5d09 100644 --- a/pkg/handler/error.go +++ b/pkg/handler/error.go @@ -105,11 +105,10 @@ func (s *Standalone) respondError(w http.ResponseWriter, r *http.Request, status return } - if level == log.WarnLevel || errors.Is(cause, context.Canceled) { - logger.Warnf(msg, cause) - } else { - logger.Errorf(msg, cause) + if errors.Is(cause, context.Canceled) { + level = log.WarnLevel } + logger.Logf(level, msg, cause) logger.Infof("errorhandler: maximum retry attempts exceeded; executing error template...") span.SetAttributes(attribute.Bool("error.retries_exhausted", true))