From 8f362cb8f64615892595a19625d3c88e00404152 Mon Sep 17 00:00:00 2001 From: Agniva De Sarker Date: Thu, 1 Sep 2022 21:01:03 +0530 Subject: [PATCH] Revert "Use error log level for websocket timeouts (#19609)" (#20929) Apparently, this can happen in normal situations as well and is causing confusion amongst customers. Reverting. This reverts commit 9534efe534d09d0378e9e1f1b51b9bb8b059bb66. ```release-note NONE ``` --- app/web_conn.go | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/app/web_conn.go b/app/web_conn.go index bc260b49bc..9970d60dab 100644 --- a/app/web_conn.go +++ b/app/web_conn.go @@ -823,10 +823,6 @@ func (wc *WebConn) logSocketErr(source string, err error) { if websocket.IsCloseError(err, websocket.CloseNormalClosure, websocket.CloseNoStatusReceived) { mlog.Debug(source+": client side closed socket", mlog.String("user_id", wc.UserId)) } else { - logFunc := mlog.Debug - if e, ok := err.(net.Error); ok && e.Timeout() { - logFunc = mlog.Error - } - logFunc(source+": closing websocket", mlog.String("user_id", wc.UserId), mlog.Err(err)) + mlog.Debug(source+": closing websocket", mlog.String("user_id", wc.UserId), mlog.Err(err)) } }