GNU bug report logs - #32443
27.0.50; encode-time bug

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 32443 in the body.
You can then email your comments to 32443 AT debbugs.gnu.org in the normal way.

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

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

From: Live System User <nyc4bos <at> aol.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 27.0.50; encode-time bug
Date: Tue, 14 Aug 2018 19:09:34 -0400

Hi,

        I am getting an "Invalid date" error when starting
        Gnus (see attachment).

        I don't get this error and Gnus starts up normally
        with Emacs 26.1.

        Thanks.




In GNU Emacs 27.0.50 (build 3, x86_64-pc-linux-gnu, GTK+ Version 3.20.10)
 of 2018-08-14 built on localhost.localdomain
Repository revision: 5620d591ee67e5b31ca8d5aa0dcc1a13116b09a7
Windowing system distributor 'Fedora Project', version 11.0.11803000
System Description: Fedora 24 (Workstation Edition)

Recent messages:
Mark set [2 times]
Saved text until "mmand-execute(execute-extended-command)
"
Mark set
Saving file /home/liveuser/gnus-date-error.txt...
Wrote /home/liveuser/gnus-date-error.txt
Read-Only mode enabled in current buffer
previous-line: Beginning of buffer [7 times]
Mark saved where search started [2 times]
previous-line: Beginning of buffer [5 times]
previous-line: Beginning of buffer
Configured using:
 'configure 'CFLAGS=-DMAIL_USE_LOCKF -O0 -ggdb3 -pipe -Wall
 -Werror=format-security -fexceptions -fstack-protector-strong
 --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic'
 LDFLAGS=-Wl,-z,relro
 --prefix=/tmp/emacs-27.0-git-master
 --with-dbus --with-gif --with-jpeg --with-png --with-rsvg --with-lcms2
 --with-tiff --with-xft --with-xpm --with-x-toolkit=gtk3 --with-gpm=yes
 --with-xwidgets --with-modules --with-json'

Configured features:
XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GSETTINGS NOTIFY
ACL LIBSELINUX GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB
TOOLKIT_SCROLL_BARS GTK3 X11 MODULES THREADS XWIDGETS JSON LCMS2 GMP

Important settings:
  value of $LANG: en_US.UTF-8
  value of $XMODIFIERS: @im=ibus
  locale-coding-system: utf-8-unix

Major mode: Text

Minor modes in effect:
  gnus-desktop-notify-mode: t
  tooltip-mode: t
  global-eldoc-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  tool-bar-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  blink-cursor-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  buffer-read-only: t
  line-number-mode: t
  transient-mark-mode: t

Load-path shadows:
None found.

Features:
(shadow sort mail-extr emacsbug help-fns radix-tree cl-print debug
backtrace cus-start timezone utf-7 nnfolder nnagent nnml gnutls
network-stream nsm gnus-agent gnus-srvr gnus-score score-mode nnvirtual
gnus-msg gnus-cache gnus-demon nntp gnus-desktop-notify notifications
dbus xml epa-file nnreddit gnus-art mm-uu mml2015 cl sieve sieve-mode
sieve-manage sasl sasl-anonymous sasl-login sasl-plain advice nnir
gnus-sum gnus-group mm-url gnus-undo gnus-start gnus-cloud nnimap nnmail
mail-source imap rfc2104 utf7 netrc parse-time gnus-spec gnus-int
gnus-range gnus-win gnus message rmc puny dired desktop frameset edmacro
kmacro dired-loaddefs subr-x format-spec rfc822 mml url url-proxy
url-privacy url-expand url-methods url-history url-cookie url-domsuf
url-util url-parse auth-source eieio eieio-core eieio-loaddefs json rx
map url-vars mm-view mml-smime smime dig mailcap mml-sec password-cache
epa epg cl-extra help-mode easymenu epg-config mm-decode mm-bodies
mm-encode mail-parse rfc2231 mailabbrev sendmail derived gmm-utils
mailheader seq byte-opt bytecomp byte-compile cconv wid-edit nnoo
nnheader gnus-util rmail dframe rmail-loaddefs rfc2047 rfc2045
ietf-drums mm-util mail-prsvr mail-utils misearch multi-isearch
elec-pair cl-seq easy-mmode cl-macs inline cl-loaddefs cl-lib gv pcase
time-date mule-util tooltip eldoc electric uniquify ediff-hook vc-hooks
lisp-float-type mwheel term/x-win x-win term/common-win x-dnd tool-bar
dnd fontset image regexp-opt fringe tabulated-list replace newcomment
text-mode elisp-mode lisp-mode prog-mode register page menu-bar
rfn-eshadow isearch timer select scroll-bar mouse jit-lock font-lock
syntax facemenu font-core term/tty-colors frame cl-generic cham georgian
utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean
japanese eucjp-ms cp51932 hebrew greek romanian slovak czech european
ethiopic indian cyrillic chinese composite charscript charprop
case-table epa-hook jka-cmpr-hook help simple abbrev obarray minibuffer
cl-preloaded nadvice loaddefs button faces cus-face macroexp files
text-properties overlay sha1 md5 base64 format env code-pages mule
custom widget hashtable-print-readable backquote threads dbusbind
inotify lcms2 dynamic-setting system-font-setting font-render-setting
xwidget-internal move-toolbar gtk x-toolkit x multi-tty
make-network-process emacs)

Memory information:
((conses 16 840321 58820)
 (symbols 48 127249 0)
 (strings 32 105403 3903)
 (string-bytes 1 4088488)
 (vectors 16 11805)
 (vector-slots 8 571636 32258)
 (floats 8 267 599)
 (intervals 56 9430 361)
 (buffers 992 34)
 (heap 1024 78672 18405))

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

From: Live System User <nyc4bos <at> aol.com>
To: 32443 <at> debbugs.gnu.org
Subject: Re: bug#32443: 27.0.50; encode-time bug
Date: Tue, 14 Aug 2018 20:00:57 -0400

[Message part 1 (text/plain, inline)]

       Here's the `encode-time' error, as an attachment.

       Thanks

[gnus-date-error.txt (text/plain, attachment)]

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

From: Live System User <nyc4bos <at> aol.com>
To: 32443 <at> debbugs.gnu.org
Subject: 27.0.50; encode-time bug
Date: Tue, 21 Aug 2018 15:52:38 -0400

Hi,

        A closer look seems to show this bug is rooted in
        a regression in (ultimately) 'parse-time-string':

           M-: (date-to-time "Tue, 06 Mar 2018 11:17:02 -0500")
           Invalid date: Tue, 06 Mar 2018 11:17:02 -0500

        When the date/time is being parsed, you erroneously get:

           M-: (parse-time-string "Tue, 06 Mar 2018 11:17:02 -0500")
           (nil nil nil 6 3 2018 2 nil nil)

        With Emacs 26.1, you get:

           (2 17 11 6 3 2018 2 nil -18000)

        Thanks.

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

From: Glenn Morris <rgm <at> gnu.org>
To: Live System User <nyc4bos <at> aol.com>
Cc: 32443 <at> debbugs.gnu.org
Subject: Re: bug#32443: 27.0.50; encode-time bug
Date: Fri, 24 Aug 2018 13:25:46 -0400

Live System User wrote:

>         When the date/time is being parsed, you erroneously get:
>
>            M-: (parse-time-string "Tue, 06 Mar 2018 11:17:02 -0500")
>            (nil nil nil 6 3 2018 2 nil nil)
>
>         With Emacs 26.1, you get:
>
>            (2 17 11 6 3 2018 2 nil -18000)

I can't reproduce this.

> System Description: Fedora 24 (Workstation Edition)

I see that distribution is EOL for one year now.
(And Fedora 25 and 26 are EOL too.)

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

From: Robert Pluim <rpluim <at> gmail.com>
To: Glenn Morris <rgm <at> gnu.org>
Cc: Live System User <nyc4bos <at> aol.com>, 32443 <at> debbugs.gnu.org
Subject: Re: bug#32443: 27.0.50; encode-time bug
Date: Wed, 29 Aug 2018 11:19:53 +0200

Glenn Morris <rgm <at> gnu.org> writes:

> Live System User wrote:
>
>>         When the date/time is being parsed, you erroneously get:
>>
>>            M-: (parse-time-string "Tue, 06 Mar 2018 11:17:02 -0500")
>>            (nil nil nil 6 3 2018 2 nil nil)
>>
>>         With Emacs 26.1, you get:
>>
>>            (2 17 11 6 3 2018 2 nil -18000)
>
> I can't reproduce this.

Iʼve seen this, but only once with a time string of "Tue, 28 Aug 2018 13:16:54
+0200". Iʼve not been able to reproduce in 'emacs -Q'.

Robert

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

From: Live System User <nyc4bos <at> aol.com>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 32443 <at> debbugs.gnu.org
Subject: Re: bug#32443: 27.0.50; encode-time bug
Date: Wed, 29 Aug 2018 11:25:31 -0400

Robert Pluim <rpluim <at> gmail.com> writes:

> Glenn Morris <rgm <at> gnu.org> writes:
>
>> Live System User wrote:
>>
>>>         When the date/time is being parsed, you erroneously get:
>>>
>>>            M-: (parse-time-string "Tue, 06 Mar 2018 11:17:02 -0500")
>>>            (nil nil nil 6 3 2018 2 nil nil)
>>>
>>>         With Emacs 26.1, you get:
>>>
>>>            (2 17 11 6 3 2018 2 nil -18000)
>>
>> I can't reproduce this.
>
> Iʼve seen this, but only once with a time string of "Tue, 28 Aug 2018 13:16:54
> +0200". Iʼve not been able to reproduce in 'emacs -Q'.

  I get the same erroreous output with "emacs -Q" with your date
  as well:


(parse-time-string "Tue, 14 Aug 2018 09:14:11 +0400")
(nil nil nil 14 8 2018 2 nil nil)


(parse-time-string "Tue, 28 Aug 2018 13:16:54 +0200")
(nil nil nil 28 8 2018 2 nil nil)

(parse-time-string "Wed, 29 Aug 2018 11:15:22 -0400")
(nil nil nil 29 8 2018 3 nil nil)



  Thanks.


>
> Robert

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

From: Robert Pluim <rpluim <at> gmail.com>
To: Live System User <nyc4bos <at> aol.com>
Cc: Glenn Morris <rgm <at> gnu.org>, 32443 <at> debbugs.gnu.org
Subject: Re: bug#32443: 27.0.50; encode-time bug
Date: Thu, 30 Aug 2018 10:24:02 +0200

Live System User <nyc4bos <at> aol.com> writes:

> Robert Pluim <rpluim <at> gmail.com> writes:
>
>> Glenn Morris <rgm <at> gnu.org> writes:
>>
>>> Live System User wrote:
>>>
>>>>         When the date/time is being parsed, you erroneously get:
>>>>
>>>>            M-: (parse-time-string "Tue, 06 Mar 2018 11:17:02 -0500")
>>>>            (nil nil nil 6 3 2018 2 nil nil)
>>>>
>>>>         With Emacs 26.1, you get:
>>>>
>>>>            (2 17 11 6 3 2018 2 nil -18000)
>>>
>>> I can't reproduce this.
>>
>> Iʼve seen this, but only once with a time string of "Tue, 28 Aug 2018 13:16:54
>> +0200". Iʼve not been able to reproduce in 'emacs -Q'.
>
>   I get the same erroreous output with "emacs -Q" with your date
>   as well:
>
>
> (parse-time-string "Tue, 14 Aug 2018 09:14:11 +0400")
> (nil nil nil 14 8 2018 2 nil nil)
>
>
> (parse-time-string "Tue, 28 Aug 2018 13:16:54 +0200")
> (nil nil nil 28 8 2018 2 nil nil)
>
> (parse-time-string "Wed, 29 Aug 2018 11:15:22 -0400")
> (nil nil nil 29 8 2018 3 nil nil)

None of those fail for me. Could you tell us which revision youʼre
currently using? Perhaps this got fixed as a side effect of some other
change, in which case I can bisect it.

Otherwise, since youʼre the only one who can reproduce it, could you
do 'edebug-defun' on 'parse-time-string' and step through it? That
might give us a better idea of what's going wrong.

Thanks

Robert

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

From: Live System User <nyc4bos <at> aol.com>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 32443 <at> debbugs.gnu.org
Subject: Re: bug#32443: 27.0.50; encode-time bug
Date: Thu, 30 Aug 2018 13:45:09 -0400

Robert Pluim <rpluim <at> gmail.com> writes:

> Live System User <nyc4bos <at> aol.com> writes:
>
>> Robert Pluim <rpluim <at> gmail.com> writes:
>>
>>> Glenn Morris <rgm <at> gnu.org> writes:
>>>
>>>> Live System User wrote:
>>>>
>>>>>         When the date/time is being parsed, you erroneously get:
>>>>>
>>>>>            M-: (parse-time-string "Tue, 06 Mar 2018 11:17:02 -0500")
>>>>>            (nil nil nil 6 3 2018 2 nil nil)
>>>>>
>>>>>         With Emacs 26.1, you get:
>>>>>
>>>>>            (2 17 11 6 3 2018 2 nil -18000)
>>>>
>>>> I can't reproduce this.
>>>
>>> Iʼve seen this, but only once with a time string of "Tue, 28 Aug 2018 13:16:54
>>> +0200". Iʼve not been able to reproduce in 'emacs -Q'.
>>
>>   I get the same erroreous output with "emacs -Q" with your date
>>   as well:
>>
>>
>> (parse-time-string "Tue, 14 Aug 2018 09:14:11 +0400")
>> (nil nil nil 14 8 2018 2 nil nil)
>>
>>
>> (parse-time-string "Tue, 28 Aug 2018 13:16:54 +0200")
>> (nil nil nil 28 8 2018 2 nil nil)
>>
>> (parse-time-string "Wed, 29 Aug 2018 11:15:22 -0400")
>> (nil nil nil 29 8 2018 3 nil nil)
>
> None of those fail for me. Could you tell us which revision youʼre
> currently using? Perhaps this got fixed as a side effect of some other
> change, in which case I can bisect it.

  I just tried it using:

Repository revision: d8bef4b519624de20baa1428dd103f61dfb220fa

   and got the same errpneous results.
>
> Otherwise, since youʼre the only one who can reproduce it, could you
> do 'edebug-defun' on 'parse-time-string' and step through it? That
> might give us a better idea of what's going wrong.


  I've never used `edebug' before so I will have to get up to speed.

  Thanks.

>
> Thanks
>
> Robert

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

From: Robert Pluim <rpluim <at> gmail.com>
To: Live System User <nyc4bos <at> aol.com>
Cc: Glenn Morris <rgm <at> gnu.org>, 32443 <at> debbugs.gnu.org
Subject: Re: bug#32443: 27.0.50; encode-time bug
Date: Fri, 31 Aug 2018 09:34:30 +0200

Live System User <nyc4bos <at> aol.com> writes:

> Robert Pluim <rpluim <at> gmail.com> writes:

>> None of those fail for me. Could you tell us which revision youʼre
>> currently using? Perhaps this got fixed as a side effect of some other
>> change, in which case I can bisect it.
>
>   I just tried it using:
>
> Repository revision: d8bef4b519624de20baa1428dd103f61dfb220fa
>
>    and got the same errpneous results.

And thatʼs more recent than my version, so the bug is still lurking
somewhere.

>>
>> Otherwise, since youʼre the only one who can reproduce it, could you
>> do 'edebug-defun' on 'parse-time-string' and step through it? That
>> might give us a better idea of what's going wrong.
>
>
>   I've never used `edebug' before so I will have to get up to speed.

SPC single steps. You can use 'e' to evaluate arbitrary expressions in
the context of the function youʼre debugging. Since single stepping
can be tedious, you can move point and use 'h' to run until you reach
point.

Robert

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

From: Live System User <nyc4bos <at> aol.com>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 32443 <at> debbugs.gnu.org
Subject: Re: bug#32443: 27.0.50; encode-time bug
Date: Sat, 22 Sep 2018 00:37:11 -0400

Robert Pluim <rpluim <at> gmail.com> writes:

> Live System User <nyc4bos <at> aol.com> writes:
>
>> Robert Pluim <rpluim <at> gmail.com> writes:
>
>>> None of those fail for me. Could you tell us which revision youʼre
>>> currently using? Perhaps this got fixed as a side effect of some other
>>> change, in which case I can bisect it.
>>
>>   I just tried it using:
>>
>> Repository revision: d8bef4b519624de20baa1428dd103f61dfb220fa
>>
>>    and got the same errpneous results.
>
> And thatʼs more recent than my version, so the bug is still lurking
> somewhere.
>
>>>
>>> Otherwise, since youʼre the only one who can reproduce it, could you
>>> do 'edebug-defun' on 'parse-time-string' and step through it? That
>>> might give us a better idea of what's going wrong.
>>
>>
>>   I've never used `edebug' before so I will have to get up to speed.
>
> SPC single steps. You can use 'e' to evaluate arbitrary expressions in
> the context of the function youʼre debugging. Since single stepping
> can be tedious, you can move point and use 'h' to run until you reach
> point.


  I'm still trying to discover where the bug is using edebug,

  Stepping through with edebug everything appears to go fine
  with going through all the rules and assigning all of its
  resultant values (such as "Tue' equals 2 gleen from
  `parse-time-weekdays '), until you get to the following:

        (rplaca (nthcdr (pop slots) time) new-val))))))))


  Once I execute `rplaca' -- "tike" and "new-val" are incorrect.
  
 FWIW, with thw recwnt update to parse-time.el (Git 0bec064), I now
 get

(parse-time-string "Tue, 21 Feb 2017 17:17:56 -0500")
 (nil nil nil 21 2 2017 2 -1 nil)


`Before this update, the "-1" was nil.

 I believe the "-1" means that DST is not known to be in effect.

 DST *is* in effect here.

`Thanks.
>
> Robert

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Live System User <nyc4bos <at> aol.com>
Cc: 32443 <at> debbugs.gnu.org
Subject: Re: bug#32443: 27.0.50; encode-time bug
Date: Fri, 27 Sep 2019 18:34:42 +0200

Live System User <nyc4bos <at> aol.com> writes:

>        Here's the `encode-time' error, as an attachment.
>
>        Thanks
>
>
> Debugger entered--Lisp error: (error "Invalid date: Tue, 06 Mar 2018 11:17:02 -0500")
>   signal(error ("Invalid date: Tue, 06 Mar 2018 11:17:02 -0500"))
>   error("Invalid date: %s" "Tue, 06 Mar 2018 11:17:02 -0500")

[...]

>   date-to-time("Tue, 06 Mar 2018 11:17:02 -0500")

I'm unable to reproduce this error:

(date-to-time "Tue, 06 Mar 2018 11:17:02 -0500")
=> (23198 48894)

Are you still seeing this in the current trunk?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Live System User <nyc4bos <at> aol.com>
Cc: 32443 <at> debbugs.gnu.org
Subject: Re: bug#32443: 27.0.50; encode-time bug
Date: Mon, 14 Oct 2019 09:34:16 +0200

Lars Ingebrigtsen <larsi <at> gnus.org> writes:

> I'm unable to reproduce this error:
>
> (date-to-time "Tue, 06 Mar 2018 11:17:02 -0500")
> => (23198 48894)
>
> Are you still seeing this in the current trunk?

More information was requested some weeks back, but no response was
given, so I'm closing this bug report.  If you're still seeing this
problem, please reopen.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

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