GNU bug report logs - #77652
Relative timestamps in mumi off by up to half an hour

Previous Next

To reply to this bug, email your comments to 77652 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "Timo Wilken" <guix <at> twilken.net>
To: <bug-mumi <at> gnu.org>
Subject: Relative timestamps in mumi off by up to half an hour
Date: Tue, 08 Apr 2025 20:56:46 +0200

Hi Arun, hi mumi'ers (mumins?),

As of now (2025-04-08 20:48 +0200), the following message displayed in mumi:

https://issues.guix.gnu.org/76718#6

...has a relative timestamp of "102 minutes ago" shown.

However, its title attribute says "Tue Apr 08 19:31:08+0200 2025", matches
when I actually sent the email, and which is a difference of only 77 minutes.

Weirdly, at 20:51, it still says "102 minutes ago", even if I force-refresh
(bypassing the browser cache).

Is there something wrong with the times that mumi assigns, or are the relative
times meant to be "fuzzy"? If so, I'd recommend rephrasing them to e.g. "about
100 minutes ago", as perfect minute-level precision in the displayed time
makes me assume that the displayed timestamp is actually that accurate!

I initially was very confused, when I saw it only 3 minutes after sending the
email, and it said "27 minutes ago"...

Cheers,
Timo

Message #8 received at 77652 <at> debbugs.gnu.org (full text, mbox):

From: Arun Isaac <arunisaac <at> systemreboot.net>
To: Timo Wilken <guix <at> twilken.net>, 77652 <at> debbugs.gnu.org
Subject: Re: bug#77652: Relative timestamps in mumi off by up to half an hour
Date: Tue, 08 Apr 2025 22:58:09 +0100

Hi Timo,

The relative timestamps are not meant to be fuzzy. This is a bug. I'll
take a look. Thanks for reporting!

Regards,
Arun

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.