From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: "A.C." Newsgroups: gmane.emacs.bugs Subject: bug#37974: eww produces "error in process filter: Specified time is not representable" Date: Tue, 29 Oct 2019 10:41:09 -0400 Message-ID: <5FBF6D88-D205-4A5A-966F-D9452321F471@gmail.com> References: <20191029003245.GA10341@arch-chirva.localdomain> <20191029045102.GA5852@D-69-91-141-110.dhcp4.washington.edu> <20191029102522.GA26999@D-69-91-141-110.dhcp4.washington.edu> <1FB46AE7-5E98-443D-950D-212F81FF5E77@gmail.com> <87wocnzpkp.fsf@gnus.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----4YY21BE17E69DZ00JNEY7IVPWA7VGW" Content-Transfer-Encoding: 7bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="85775"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: K-9 Mail for Android Cc: 37974@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Oct 29 15:42:21 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iPShP-000M9Q-9p for geb-bug-gnu-emacs@m.gmane.org; Tue, 29 Oct 2019 15:42:19 +0100 Original-Received: from localhost ([::1]:57860 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iPShN-0001EC-NX for geb-bug-gnu-emacs@m.gmane.org; Tue, 29 Oct 2019 10:42:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35761) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iPShE-0001Dr-00 for bug-gnu-emacs@gnu.org; Tue, 29 Oct 2019 10:42:09 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iPShB-0002Z2-Hz for bug-gnu-emacs@gnu.org; Tue, 29 Oct 2019 10:42:07 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39638) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iPShB-0002Yw-F5 for bug-gnu-emacs@gnu.org; Tue, 29 Oct 2019 10:42:05 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iPShB-0002s5-BD for bug-gnu-emacs@gnu.org; Tue, 29 Oct 2019 10:42:05 -0400 X-Loop: help-debbugs@gnu.org Resent-From: "A.C." Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 29 Oct 2019 14:42:05 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 37974 X-GNU-PR-Package: emacs X-Debbugs-Original-Cc: 37974@debbugs.gnu.org, bug-gnu-emacs@gnu.org Original-Received: via spool by submit@debbugs.gnu.org id=B.157236008610966 (code B ref -1); Tue, 29 Oct 2019 14:42:05 +0000 Original-Received: (at submit) by debbugs.gnu.org; 29 Oct 2019 14:41:26 +0000 Original-Received: from localhost ([127.0.0.1]:48455 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iPSgV-0002qk-22 for submit@debbugs.gnu.org; Tue, 29 Oct 2019 10:41:26 -0400 Original-Received: from lists.gnu.org ([209.51.188.17]:34730) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1iPSgT-0002qW-14 for submit@debbugs.gnu.org; Tue, 29 Oct 2019 10:41:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35703) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iPSgR-0000uK-Bg for bug-gnu-emacs@gnu.org; Tue, 29 Oct 2019 10:41:20 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iPSgP-0002Of-Rr for bug-gnu-emacs@gnu.org; Tue, 29 Oct 2019 10:41:19 -0400 Original-Received: from mail-qk1-x72e.google.com ([2607:f8b0:4864:20::72e]:45672) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iPSgP-0002OP-NO for bug-gnu-emacs@gnu.org; Tue, 29 Oct 2019 10:41:17 -0400 Original-Received: by mail-qk1-x72e.google.com with SMTP id q70so12421187qke.12 for ; Tue, 29 Oct 2019 07:41:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:subject:to:cc:from:message-id; bh=AHr4flOSyC7XUOAwxOGshrkRq+A9aIcEotzp7zt27qo=; b=aVTbKLW0AoZZO6co6XOEfkpFbztlsCWNfOAKtj6362AyRNy7lnUlagduPLiAqqW1IZ iiubjgdMUxnTKpBiifN2PV+cmlOGWLq8iu7KlFxiWtpMyw4lbar4Enasm4pwbv4IC0nQ 8SAsqJr+JFXylpQeNttjAYbjUndg/KA2/PYIfaH/LhTVW+oqMi2eoXJwyzlsGVQMCfLM amaI5f6GKm/JIYVqLjKMeGSs46OXxQ9v/zkGST9NG6qDn6znvvHxJG7NYFe/Wp3zqcLc OaS6YJENtoV9IzEtxO6hXtKaEPJ8GVN7uYJsOWGihfA/0b1Z/DRBc8SY9NcCtsPnRzb0 BgTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:to:cc:from :message-id; bh=AHr4flOSyC7XUOAwxOGshrkRq+A9aIcEotzp7zt27qo=; b=bN2gKggWzCOmRt/kTGljiRowAn0bLYSzkG9wMuKe9V0xUUz+R453LAJox5LyXrBcUc fD4RU6tPSyiovt8C8lxPeME+wvLVV7oxARfV3zSLSQ4S+OoRrG7SPNcPrfTJp5YtVhpZ V/wSnpyF2YEX/UNSqVE5C1L5ygZ5HSUjD7zWCOuRs4QFWv+5SfBGvvTMBokjday5iruO 5YFd2cIW09x5IzENwQE+UgFUDbYKh9geEHumk/HrzKZ5QlpaEHaVCsf2Jxtf85cAOUBL V0NzeZImi3TEboEa6imtWaxnhG1ED6l2juOT9rAZj2HYDX9jJFo/6Hb/z7xrEZz/jQCz ypaQ== X-Gm-Message-State: APjAAAXEHpTB+aVz5n8ZCkS2WKlnjfU0rsk0qqcmAHk7cLzvyS23s7YO zXM+4v5Hgw9QcK3QQXKpJijJBfKs X-Google-Smtp-Source: APXvYqzz4iQomhWsltEDqp2G3dJPTz/KTkuD4cjFdyhBb9H9r7N7S+zO8Xc9t4CB0XKuu+FWkpIWVQ== X-Received: by 2002:a05:620a:208a:: with SMTP id e10mr22126223qka.189.1572360076884; Tue, 29 Oct 2019 07:41:16 -0700 (PDT) Original-Received: from [192.168.1.171] (pool-68-133-6-220.bflony.fios.verizon.net. [68.133.6.220]) by smtp.gmail.com with ESMTPSA id g83sm7594534qke.100.2019.10.29.07.41.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Oct 2019 07:41:15 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. 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: 209.51.188.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:170375 Archived-At: ------4YY21BE17E69DZ00JNEY7IVPWA7VGW Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable OK, so it *is* a 32-bit problem=2E This is awesome :): - on my 32-bit system the highest I can go with an error-less format-time-= string is=20 (format-time-string "%a %b %d %H:%M:%S %Y GMT" (list 32767 65535 0 0)) That will give a total of=20 32767*2**16+65535 =3D 2147483647 =3D 2**31-1 seconds from the Unix epoch, i=2Ee=2E spot-on the year-2038 problem: https://en=2Em=2Ewikipedia=2Eorg/wiki/Year_2038_problem - on the other hand, on my 64-bit systems the highest I can go is=20 (format-time-string "%a %b %d %H:%M:%S %Y GMT" (list 1034058169428 61391 0= 0)) This puzzled me a bit, but looking at the date, it's Wed Dec 31 23:59:59 G= MT year (wait for it) 2147485547 =3D 1900 + 2**31-1 So it's again the usual issue, kicked up to higher timestamps in the 64-bi= t case: http://www=2Eunixguide=2Enet/sun/faq/6=2E27=2Eshtml On October 29, 2019 10:06:28 AM EDT, "A=2EC=2E" w= rote: > > >On October 29, 2019 8:47:02 AM EDT, Lars Ingebrigtsen >wrote: >>"A=2EC=2E" writes: >> >>> On the other hand, the Debian i686 system that doesn't load >arxiv=2Eorg >>has a >>> largest valid n of >> >>I'm not quite sure I understood the bug report -- are you saying that >>this is only an issue on 32-bit systems? >> > >I don't have access to enough systems to tell for sure=2E I do know it's >only happening on the one 32-bit system I have access to right now, and >also that I hit the problem a while back on 32-bit ARM: > >https://github=2Ecom/termux/termux-packages/issues/2614 > >(and have not see the issue on any 64-bit systems) > >>In any case, Emacs 27 has bignum support, so this should hopefully not >>be a problem any more=2E Can you try the test case with the current >>Emacs >>trunk and see whether it's still present? > >That will be tough=2E This 32-bit machine overheats something fierce; I >doubt I can even clone the git repo without it dying, let alone >compile=2E > >--=20 >Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E ------4YY21BE17E69DZ00JNEY7IVPWA7VGW Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable OK, so it *is* a 32-bit problem=2E This is awesome= :):

- on my 32-bit system the highest I can go with an error-less f= ormat-time-string is

(format-time-string "%a %b %d %H:%M:%S %Y GMT"= (list 32767 65535 0 0))

That will give a total of

32767*2**= 16+65535 =3D 2147483647 =3D 2**31-1

seconds from the Unix epoch, i= =2Ee=2E spot-on the year-2038 problem:

https://en=2Em=2Ewikipedia=2Eorg/wik= i/Year_2038_problem

- on the other hand, on my 64-bit systems th= e highest I can go is

(format-time-string "%a %b %d %H:%M:%S %Y GMT= " (list 1034058169428 61391 0 0))

This puzzled me a bit, but looking= at the date, it's Wed Dec 31 23:59:59 GMT year (wait for it)

214748= 5547 =3D 1900 + 2**31-1

So it's again the usual issue, kicked up to = higher timestamps in the 64-bit case:

http://www=2Eunixguide=2Enet/sun/faq/6=2E= 27=2Eshtml

On October 29, 2019 10:06:= 28 AM EDT, "A=2EC=2E" <achirvasub@gmail=2Ecom> wrote:


On October 29, 2019 8:47:02 AM EDT, Lars Ingebrigtsen <larsi@gn= us=2Eorg> wrote:
>"A=2EC=2E" <achirvasub@gmail=2Ecom> writes= :
>
>> On the other hand, the Debian i686 system that doesn'= t load arxiv=2Eorg
>has a
>> largest valid n of
>
&= gt;I'm not quite sure I understood the bug report -- are you saying that>this is only an issue on 32-bit systems?
>

I don't have a= ccess to enough systems to tell for sure=2E I do know it's only happening o= n the one 32-bit system I have access to right now, and also that I hit the= problem a while back on 32-bit ARM:

https://github=2Ecom/termux/termux-pac= kages/issues/2614

(and have not see the issue on any 64-bit syst= ems)

>In any case, Emacs 27 has bignum support, so this should ho= pefully not
>be a problem any more=2E Can you try the test case with= the current
>Emacs
>trunk and see whether it's still present?<= br>
That will be tough=2E This 32-bit machine overheats something fierce= ; I doubt I can even clone the git repo without it dying, let alone compile= =2E

--
Sent from my Android device with K-9 M= ail=2E Please excuse my brevity=2E ------4YY21BE17E69DZ00JNEY7IVPWA7VGW--