Does this issue over in knitr shed some additional light ...
https://github.com/yihui/knitr/issues/2338
Tim
On 07/06/2024 14:50, Ivan Krylov via R-package-devel wrote:
В Fri, 7 Jun 2024 09:10:03 +0200
"C.H." пишет:
RMarkdown vignettes are sometimes used to demonstrate errors and one
can
On Wed, 10 Apr 2024, at 11:52 AM, Martin Maechler wrote:
>>>>>> Tim Taylor
>>>>>> on Wed, 10 Apr 2024 10:37:00 +0100 writes:
>
> > Hi Mikael Revisiting this. Have the plans changed for
> > 1.7-0 release?
>
> > Tim
&g
Hi Mikael
Revisiting this. Have the plans changed for 1.7-0 release?
Tim
On Mon, 12 Feb 2024, at 6:36 PM, Mikael Jagan wrote:
> Dear users and binary repository maintainers,
>
> We are preparing Matrix version 1.7-0 for CRAN submission on March 11, ahead
> of the spring release of R version
This is just a punt from a quick glance at your tests. Try using the following
on your local build to ensure it's not a time zone issue
`TZ=NZ R CMD check --as-cran`
`Apologies if this is just noise but whenever I've had issues with datetimes
and mac tests this is the first thing I check.`
Could you have been caught out with the precompiled binary that serde started
distributing in a few of it’s versions
(https://github.com/serde-rs/serde/issues/2538)? That could have been a reason
if you pinned a version with it present but only CRAN could confirm if that was
the reason.
Tim
I’m definitely sympathetic to both sides but have come around to the view of
Greg, Dirk et al. It seems sensible to have a default that benefits the
majority of “normal” users and require explicit action in shared environments
not vice-versa.
That is not to say that data.table could not do
names(value) <- deparse1(substitute(x))
value
}
Kind regards
Enrico
Vincent
On Thu, 6 Jul 2023 at 10:41, Tim Taylor
wrote:
Apologies - I've not had enough caffeine just yet. The reprex below
highlights the issue but I think the code which implemented the change
*may* ne
Apologies - I've not had enough caffeine just yet. The reprex below
highlights the issue but I think the code which implemented the change
*may* need tweaking not lapply.
Tim
On 06/07/2023 09:26, Tim Taylor wrote:
This *may* be an issue in lapply. Let's see what others day. Reprex
below
This *may* be an issue in lapply. Let's see what others day. Reprex below
Sys.setenv("_R_CHECK_AS_DATA_FRAME_EXPLICIT_METHOD_" = TRUE)
dat <- Sys.Date()
as.data.frame(dat)
#> dat
#> 1 2023-07-06
lapply(dat, as.data.frame)
#> Warning: Direct call of 'as.data.frame.Date()' is deprecated.
On 12/05/2023 08:47, Iñaki Ucar wrote:
El vie., 12 may. 2023 5:58, Simon Urbanek
escribió:
I think it would be quite useful to have some community repository of code
snippets dealing with such situations. R-exts gives advice and pieces of
code which are useful, but they are not complete
No direct experience, so others may know more, but I'd have thought in the
system requirements of DESCRIPTION. See for instance what duckdb does
https://github.com/duckdb/duckdb/blob/master/tools/rpkg/DESCRIPTION
From: R-package-devel on behalf of Reed
)
**
Cheers
On Thu, 10 Dec 2020 at 10:02, Uwe Ligges
wrote:
>
> WHich package? Where are the logs?
>
> Best,
> Uwe Ligges
>
>
> On 10.12.2020 10:39, Tim Taylor wrote:
> > Morning all
> >
> > What
Morning all
What's the best way to narrow down test errors that are occurring on
win-builder only? I've tried checking the package on local installs
of r-devel (both 32 bit and 64bit), and on the Windows installs on
rhub and through GitHub actions. On all of these systems the checks
pass
I've made an example at https://github.com/tjtnew/newbies that uses
GitHub actions to monitor how many hours a package has been in the
"newbies" queue. It updates hourly and saves to a csv in the repo.
It's not something I have time to develop more but if someone wants to
pick it up and take it
14 matches
Mail list logo
