Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.128.48; helo=mail-wm1-f48.google.com; envelope-from=hugo@yunojuno.com; receiver=<UNKNOWN> 
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: [PATCH django-impersonate] Downgrade signals logging from warning to
 debug
Message-Id: <bd1429321fb4a7f46274.1607609806@YJ-LDN-MBA-033>
User-Agent: Mercurial-patchbomb/5.6.1
Date: Thu, 10 Dec 2020 14:16:46 +0000
From: Hugo Rodger-Brown <hugo@yunojuno.com>
To: ~petersanchez/public-inbox@lists.code.netlandish.com
Cc: hugo@yunojuno.com

# HG changeset patch
# User Hugo Rodger-Brown <hugo@yunojuno.com>
# Date 1607608487 0
#      Thu Dec 10 13:54:47 2020 +0000
# Branch downgrade-logging
# Node ID bd1429321fb4a7f4627448681d369d07875c5edf
# Parent  a174b1c67a73699e1ea51d1433db7d0f22c4e6ef
Downgrade signals logging from warning to debug

In production we are seeing the warnings raised by the
signals appearing frequently. I believe this is caused by
people having multiple tabs open, stopping impersonating
in one, and then some time later clicking the stop impersonate
link in another. This is a completely valid use case, and
shouldn't raise a warning.

diff --git a/impersonate/signals.py b/impersonate/signals.py
--- a/impersonate/signals.py
+++ b/impersonate/signals.py
@@ -87,7 +87,7 @@
         log.session_ended_at = tz_now()
         log.save()
     except ImpersonationLog.DoesNotExist:
-        logger.warning(
+        logger.debug(
             (u'Unfinished ImpersonationLog could not be found for: '
              u'{0}, {1}, {2}').format(
                  impersonator,
@@ -96,7 +96,7 @@
              )
         )
     except ImpersonationLog.MultipleObjectsReturned:
-        logger.warning(
+        logger.debug(
             (u'Multiple unfinished ImpersonationLog matching: '
              u'{0}, {1}, {2}').format(
                  impersonator,