unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "A.C." <achirvasub@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 37974@debbugs.gnu.org
Subject: bug#37974: eww produces "error in process filter: Specified time is not representable"
Date: Tue, 29 Oct 2019 10:41:09 -0400	[thread overview]
Message-ID: <5FBF6D88-D205-4A5A-966F-D9452321F471@gmail.com> (raw)
In-Reply-To: <EA2E4420-0B85-4C98-9183-B2D3227937A9@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2101 bytes --]

OK, so it *is* a 32-bit problem. This is awesome :):

- on my 32-bit system the highest I can go with an error-less format-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 = 2147483647 = 2**31-1

seconds from the Unix epoch, i.e. spot-on the year-2038 problem:

https://en.m.wikipedia.org/wiki/Year_2038_problem

- on the other hand, on my 64-bit systems the 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)

2147485547 = 1900 + 2**31-1

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

http://www.unixguide.net/sun/faq/6.27.shtml

On October 29, 2019 10:06:28 AM EDT, "A.C." <achirvasub@gmail.com> wrote:
>
>
>On October 29, 2019 8:47:02 AM EDT, Lars Ingebrigtsen <larsi@gnus.org>
>wrote:
>>"A.C." <achirvasub@gmail.com> writes:
>>
>>> On the other hand, the Debian i686 system that doesn't load
>arxiv.org
>>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. 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.com/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.  Can you try the test case with the current
>>Emacs
>>trunk and see whether it's still present?
>
>That will be tough. This 32-bit machine overheats something fierce; I
>doubt I can even clone the git repo without it dying, let alone
>compile.
>
>-- 
>Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[-- Attachment #2: Type: text/html, Size: 2555 bytes --]

  reply	other threads:[~2019-10-29 14:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29  0:32 bug#37974: eww produces "error in process filter: Specified time is not representable" Stuart Little
2019-10-29  4:51 ` Stuart Little
2019-10-29 10:25   ` Stuart Little
2019-10-29 12:05     ` A.C.
2019-10-29 12:47       ` Lars Ingebrigtsen
2019-10-29 14:06         ` A.C.
2019-10-29 14:41           ` A.C. [this message]
2019-10-29 21:52           ` Lars Ingebrigtsen
2019-10-29 22:23             ` A.C.
2019-10-30 10:19               ` Colin Baxter
2019-10-30 11:01                 ` Lars Ingebrigtsen
2019-10-31 18:50                   ` A.C.
2019-11-01 13:46                     ` Lars Ingebrigtsen
2019-11-01  8:05 ` Paul Eggert
2019-11-01 23:22   ` Paul Eggert
2019-11-02  7:34     ` Eli Zaretskii

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5FBF6D88-D205-4A5A-966F-D9452321F471@gmail.com \
    --to=achirvasub@gmail.com \
    --cc=37974@debbugs.gnu.org \
    --cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).