From 740e4f2bd6dfd1b6a5143384ab03d2627c31ac2b Mon Sep 17 00:00:00 2001
From: Hanno Cornelius <68783915+jm-clius@users.noreply.github.com>
Date: Tue, 14 Feb 2023 15:07:26 +0200
Subject: [PATCH] chore: lower per-message log level to trace (#1561)

---
 waku/v2/node/message_cache.nim | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/waku/v2/node/message_cache.nim b/waku/v2/node/message_cache.nim
index f3d361a69..2d66ca793 100644
--- a/waku/v2/node/message_cache.nim
+++ b/waku/v2/node/message_cache.nim
@@ -53,7 +53,7 @@ proc addMessage*[K](t: MessageCache, topic: K, msg: WakuMessage) =
   var messages = t.table.getOrDefault(topic, @[])
 
   if messages.len >= t.capacity.int:
-    debug "Topic cache capacity reached", topic=topic
+    trace "Topic cache capacity reached", topic=topic
     # Message cache on this topic exceeds maximum. Delete oldest.
     # TODO: this may become a bottle neck if called as the norm rather than 
     #  exception when adding messages. Performance profile needed.