From: Mark H Weaver <mhw@netris.org>
To: Zefram <zefram@fysh.org>
Cc: 22034-done@debbugs.gnu.org
Subject: bug#22034: time-utc->date shows bogus zone-dependent leap second
Date: Sat, 20 Oct 2018 17:42:02 -0400 [thread overview]
Message-ID: <87a7n847o5.fsf@netris.org> (raw)
In-Reply-To: <20151127195146.GB28472@fysh.org> (Zefram's message of "Fri, 27 Nov 2015 19:51:46 +0000")
Zefram <zefram@fysh.org> writes:
> time-utc->date seems to think that a leap second occurs at a different
> time in each time zone:
>
> scheme@(guile-user)> (use-modules (srfi srfi-19))
> scheme@(guile-user)> (define (tdate d) (write (list (date->string d "~4") (date->string (time-utc->date (date->time-utc d) 3600) "~4"))) (newline))
> scheme@(guile-user)> (tdate (make-date 0 59 59 22 30 6 2012 0))
> ("2012-06-30T22:59:59Z" "2012-06-30T23:59:59+0100")
> scheme@(guile-user)> (tdate (make-date 0 0 0 23 30 6 2012 0))
> ("2012-06-30T23:00:00Z" "2012-06-30T23:59:60+0100")
> scheme@(guile-user)> (tdate (make-date 0 1 0 23 30 6 2012 0))
> ("2012-06-30T23:00:01Z" "2012-07-01T00:00:01+0100")
>
> These are three consecutive seconds that occur an hour before a genuine
> leap second (at 23:59:60Z). Observe that time-utc->date, applied to the
> middle second, describes it as a leap second happening at 23:59:60+01:00,
> which is bogus. [...]
This is fixed by commit 5106377a3460e1e35daf14ea6edbe80426347155 on the
stable-2.2 branch.
> Matching up with this, the actual leap second is never correctly described
> with a non-zero zone offset. It should be, for example, 00:59:60+01:00.
If I understand correctly, 'time-utc->date' should never return a date
object with 60 in the seconds field, because those extra seconds have no
representation in time-utc. They only have representations in time-tai
and time-monotonic.
Anyway, thanks very much for these reports! I'm closing this bug now,
but feel free to reopen if you think there are still issues to resolve.
Mark
next prev parent reply other threads:[~2018-10-20 21:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 19:51 bug#22034: time-utc->date shows bogus zone-dependent leap second Zefram
2018-10-20 21:42 ` Mark H Weaver [this message]
2018-10-22 2:38 ` John Cowan
2018-10-22 6:12 ` Mark H Weaver
2018-10-25 22:21 ` John Cowan
2018-10-28 20:39 ` Mark H Weaver
2018-10-28 23:58 ` John Cowan
2018-10-29 7:16 ` Mark H Weaver
2018-10-29 22:33 ` Mark H Weaver
2018-10-30 0:23 ` John Cowan
2018-10-30 2:12 ` Mark H Weaver
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7n847o5.fsf@netris.org \
--to=mhw@netris.org \
--cc=22034-done@debbugs.gnu.org \
--cc=zefram@fysh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).