From d092a01ceaa7bbce48b708c9c8a5a2d2e131fbe7 Mon Sep 17 00:00:00 2001
From: Jeremy Kescher <jeremy@kescher.at>
Date: Tue, 14 Mar 2023 09:45:50 +0100
Subject: [PATCH] Use Rails.logger.warn instead of puts

---
 app/controllers/concerns/cache_concern.rb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/app/controllers/concerns/cache_concern.rb b/app/controllers/concerns/cache_concern.rb
index fb4016f55f..4386015f22 100644
--- a/app/controllers/concerns/cache_concern.rb
+++ b/app/controllers/concerns/cache_concern.rb
@@ -41,12 +41,12 @@ module CacheConcern
         true
       end
 
-      $stderr.puts "fetch_value issue culprit: #{culprit.inspect}\n"
+      Rails.logger.warn "fetch_value issue culprit: #{culprit.inspect}"
 
       cache_key = Rails.cache.send(:normalize_key, culprit, {})
       entry = Rails.cache.send(:read_entry, cache_key)
       raw_marshal = Zlib::Inflate.inflate(entry.instance_variable_get(:@value))
-      $stderr.puts "base64 marshal of culprit: #{Base64.encode64(raw_marshal)}"
+      Rails.logger.warn "base64 marshal of culprit: #{Base64.encode64(raw_marshal)}"
     end
 
     return [] if raw.empty?