From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!.POSTED!not-for-mail
From: Mark H Weaver <mhw@netris.org>
Newsgroups: gmane.lisp.guile.bugs
Subject: bug#26164: time-difference mishandles leap seconds
Date: Sun, 21 Oct 2018 18:56:54 -0400
Message-ID: <8736syzz61.fsf@netris.org>
References: <20170318224126.GK6518@fysh.org>
NNTP-Posting-Host: blaine.gmane.org
Mime-Version: 1.0
Content-Type: text/plain
X-Trace: blaine.gmane.org 1540163378 3076 195.159.176.226 (21 Oct 2018 23:09:38 GMT)
X-Complaints-To: usenet@blaine.gmane.org
NNTP-Posting-Date: Sun, 21 Oct 2018 23:09:38 +0000 (UTC)
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
Cc: 26164@debbugs.gnu.org
To: Zefram <zefram@fysh.org>
Original-X-From: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Mon Oct 22 01:09:34 2018
Return-path: <bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org>
Envelope-to: guile-bugs@m.gmane.org
Original-Received: from lists.gnu.org ([208.118.235.17])
	by blaine.gmane.org with esmtp (Exim 4.84_2)
	(envelope-from <bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org>)
	id 1gEMqj-0000iM-Hh
	for guile-bugs@m.gmane.org; Mon, 22 Oct 2018 01:09:33 +0200
Original-Received: from localhost ([::1]:60545 helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org>)
	id 1gEMsq-000637-3e
	for guile-bugs@m.gmane.org; Sun, 21 Oct 2018 19:11:44 -0400
Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41946)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gEMrn-00052L-Sq
	for bug-guile@gnu.org; Sun, 21 Oct 2018 19:10:46 -0400
Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gEMfa-000655-Ri
	for bug-guile@gnu.org; Sun, 21 Oct 2018 18:58:07 -0400
Original-Received: from debbugs.gnu.org ([208.118.235.43]:58832)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1gEMfa-00064r-Ku
	for bug-guile@gnu.org; Sun, 21 Oct 2018 18:58:02 -0400
Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1gEMfa-00073g-Gw
	for bug-guile@gnu.org; Sun, 21 Oct 2018 18:58:02 -0400
X-Loop: help-debbugs@gnu.org
Resent-From: Mark H Weaver <mhw@netris.org>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-CC: bug-guile@gnu.org
Resent-Date: Sun, 21 Oct 2018 22:58:02 +0000
Resent-Message-ID: <handler.26164.B26164.154016263727050@debbugs.gnu.org>
Resent-Sender: help-debbugs@gnu.org
X-GNU-PR-Message: followup 26164
X-GNU-PR-Package: guile
X-GNU-PR-Keywords: 
Original-Received: via spool by 26164-submit@debbugs.gnu.org id=B26164.154016263727050
	(code B ref 26164); Sun, 21 Oct 2018 22:58:02 +0000
Original-Received: (at 26164) by debbugs.gnu.org; 21 Oct 2018 22:57:17 +0000
Original-Received: from localhost ([127.0.0.1]:34857 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces@debbugs.gnu.org>)
	id 1gEMer-00072D-HT
	for submit@debbugs.gnu.org; Sun, 21 Oct 2018 18:57:17 -0400
Original-Received: from world.peace.net ([64.112.178.59]:36496)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <mhw@netris.org>) id 1gEMep-00071y-HC
	for 26164@debbugs.gnu.org; Sun, 21 Oct 2018 18:57:15 -0400
Original-Received: from mhw by world.peace.net with esmtpsa
	(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89)
	(envelope-from <mhw@netris.org>)
	id 1gEMej-0003H3-DS; Sun, 21 Oct 2018 18:57:09 -0400
In-Reply-To: <20170318224126.GK6518@fysh.org> (Zefram's message of "Sat, 18
	Mar 2017 22:41:26 +0000")
X-BeenThere: debbugs-submit@debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 208.118.235.43
X-BeenThere: bug-guile@gnu.org
List-Id: "Bug reports for GUILE,
	GNU's Ubiquitous Extension Language" <bug-guile.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guile>,
	<mailto:bug-guile-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guile/>
List-Post: <mailto:bug-guile@gnu.org>
List-Help: <mailto:bug-guile-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guile>,
	<mailto:bug-guile-request@gnu.org?subject=subscribe>
Errors-To: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org
Original-Sender: "bug-guile" <bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org>
Xref: news.gmane.org gmane.lisp.guile.bugs:9234
Archived-At: <http://permalink.gmane.org/gmane.lisp.guile.bugs/9234>

Zefram <zefram@fysh.org> writes:

> Computing the duration of the period between two UTC times, using
> SRFI-19 mechanisms:
>
> scheme@(guile-user)> (use-modules (srfi srfi-19))
> scheme@(guile-user)> (define t0 (date->time-utc (make-date 0 59 59 23 30 6 2012 0))) 
> scheme@(guile-user)> (define t1 (date->time-utc (make-date 0 1 0 0 1 7 2012 0)))
> scheme@(guile-user)> (time-difference t1 t0)
> $1 = #<time type: time-duration nanosecond: 0 second: 2>
>
> The two times are 2012-06-30T23:59:59 and 2012-07-01T00:00:01, so at
> first glance one would expect the duration to be 2 s as shown above,
> the two seconds being 23:59:59 and 00:00:00.  But in fact there was
> a leap second 2012-06-30T23:59:60, so the duration of this period is
> actually 3 s.

You seem to be assuming that SRFI-19 durations should _always_ represent
intervals of TAI time.  While I agree that TAI time is often the right
choice for durations, there are other cases where monotonic time is a
better choice.  Currently, monotonic time == TAI time, but SRFI-19 makes
it clear that this needn't be the case, and at some point we might want
to change monotonic time to be _truly_ monotonic, even in cases where
the system clock jumps backward.

Durations in UTC time have uses as well.  For example, every UTC day has
exactly 86400 UTC seconds, so (make-time time-duration 0 86400) means 1
UTC day, when added to a UTC time.  This is a duration that, when added
to any UTC time, always leaves the time-of-day unchanged.  There is no
fixed duration of TAI time that has this property, because not all UTC
days have the same number of TAI seconds.

> [...]  Since 1972, the seconds of UTC are of exactly
> the same duration as the seconds of TAI.  (They're also phase-locked to
> TAI seconds.)  Thus the period of three TAI seconds is also a period of
> three UTC seconds.  It is not somehow squeezed into two UTC seconds.

I believe you are mistaken here.  Not all UTC seconds have the same
duration as a TAI second.  Some TAI seconds correspond to 0 UTC seconds,
and maybe some day there will be a TAI second that corresponds to 2 UTC
seconds.

Having said all of this, I should admit that I'm not an expert on time
standards, so perhaps I've misunderstood something.

What do you think?

      Mark