[Tools-discuss] over-zealous mail-send notification caching?

Benjamin Kaduk <kaduk@mit.edu> Tue, 11 August 2020 00:59 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9B223A0E73 for <tools-discuss@ietfa.amsl.com>; Mon, 10 Aug 2020 17:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BQOcsCjAl0xd for <tools-discuss@ietfa.amsl.com>; Mon, 10 Aug 2020 17:59:32 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BD0E3A0E71 for <tools-discuss@ietf.org>; Mon, 10 Aug 2020 17:59:32 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 07B0xS7w028766 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <tools-discuss@ietf.org>; Mon, 10 Aug 2020 20:59:30 -0400
Date: Mon, 10 Aug 2020 17:59:28 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: tools-discuss@ietf.org
Message-ID: <20200811005928.GZ92412@kduck.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/km6nx5jnjIEBsniBkCnrqCshayw>
Subject: [Tools-discuss] over-zealous mail-send notification caching?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Aug 2020 00:59:34 -0000

Hi all,

I'm not really sure the best way to describe this, but recently (the past
few days, maybe) I've been getting a lot more of the yellow "Email was
sent" notices at the top of the page after I perform an operation that
sends mail.  In particular, I'll get the notice about mail sent by a
previous operation (just now I got some from as far back as August 7th),
and having previously dismissed any given notification does not seem to
prevent me from seeing it again after a subsequent operation.

Having the whole page taken up by "Email was sent" notices is a bit
distracting :)

I'm not sure how much more information is needed for an actionable report;
I'll try to take better notes as to whether I only see this after an action
that itself generates an email (vs other page loads).  Possibly relatedly
(to the over-zealous caching), I have been seeing sporadic instances where
doing something that sends mail (possibly only entering a ballot position,
but I'm not 100% sure) leaves me at a page other than the page I was coming
from (i.e., some other document entirely).  Perhaps a common thread is that
I have multiple datatracker tabs open and I've done some other operation in
between starting to ballot and finishing, and the operation in the other
tab overwrites the per-tab state for where to send me back to?  This has
been happening for longer than the overly persistent "Email was sent"
notices, though -- months, probably.

Thanks,

Ben