Confirmed on Fedora 36 which has a 32-bit time_t for an i686 compile. I
was a bit surprised that has not been changed, but gather Linux distros
are preferring to drop ix86 than fix it.
There is a simple workaround, to configure R with
--with-internal-tzcode, which always uses a 64-bit time_t.
> Davis Vaughan
> on Fri, 7 Oct 2022 11:00:23 -0400 writes:
> Martin,
> FWIW, I scoured the docs using GitHub's new code search preview but can't
> seem to find any reference to the fact that POSIXlt fields are internally
> recycled (even though lubridate seems to have
Martin,
FWIW, I scoured the docs using GitHub's new code search preview but can't
seem to find any reference to the fact that POSIXlt fields are internally
recycled (even though lubridate seems to have been relying on this for
quite some time).
-Davis
On Fri, Oct 7, 2022 at 8:52 AM Martin Maechl
> Martin Maechler
> on Thu, 6 Oct 2022 10:15:29 +0200 writes:
> Davis Vaughan
> on Wed, 5 Oct 2022 17:04:11 -0400 writes:
>> Hi all,
>> I think I have discovered a bug in the conversion from POSIXlt to Date
that
>> has been introduced in r-devel.
>> It
On 06/10/2022 09:41, Berwin A Turlach wrote:
G'day all,
On Thu, 6 Oct 2022 10:15:29 +0200
Martin Maechler wrote:
Davis Vaughan
on Wed, 5 Oct 2022 17:04:11 -0400 writes:
> # Weird, where is the `NA`?
> as.Date(x)
> #> [1] "2013-01-31" "1970-01-01" "2013-03-31"
> ```
G'day all,
On Thu, 6 Oct 2022 10:15:29 +0200
Martin Maechler wrote:
> > Davis Vaughan
> > on Wed, 5 Oct 2022 17:04:11 -0400 writes:
> > # Weird, where is the `NA`?
> > as.Date(x)
> > #> [1] "2013-01-31" "1970-01-01" "2013-03-31"
> > ```
>
> I agree that the
> Davis Vaughan
> on Wed, 5 Oct 2022 17:04:11 -0400 writes:
> Hi all,
> I think I have discovered a bug in the conversion from POSIXlt to Date
that
> has been introduced in r-devel.
> It affects lubridate, but surprisingly didn't cause test failures there.
> Ins
Hi all,
I think I have discovered a bug in the conversion from POSIXlt to Date that
has been introduced in r-devel.
It affects lubridate, but surprisingly didn't cause test failures there.
Instead it caused test failures in users of lubridate, like slider, arrow,
and admiral (see https://github.c
