similar to: R-devel internal errors during check produce?

>>>>> Jan Gorecki writes: > So the unique.default is from the R tools package during checks. > I don't see those issues on CRAN checks. I cannot reproduce this locally (and have no clues about docker). Perhaps you can try to debug this on your end? And see what env_list is when the error occurs? Best -k > Exact environment where I am reproducing this issue is a

Thank you both, You are absolutely correct that example should be minimal, so here it is. l = list(a=new.env(), b=new.env()) unique(l) Just for completeness, env_list during check that raises error env_list <- list(baseenv(), as.environment("package:graphics"), as.environment("package:stats"), as.environment("package:utils"),

>>>>> Jan Gorecki writes: > Thank you both, > You are absolutely correct that example should be minimal, so here it is. > l = list(a=new.env(), b=new.env()) > unique(l) > Just for completeness, env_list during check that raises error > env_list <- list(baseenv(), > as.environment("package:graphics"), >

>>>>> Kurt Hornik >>>>> on Mon, 29 Jun 2020 16:13:03 +0200 writes: >>>>> Jan Gorecki writes: >> So the unique.default is from the R tools package during >> checks. I don't see those issues on CRAN checks. > I cannot reproduce this locally (and have no clues about > docker). Perhaps you can try to debug this

So the unique.default is from the R tools package during checks. I don't see those issues on CRAN checks. Exact environment where I am reproducing this issue is a fresh ubuntu, no R packages pre-installed docker pull registry.gitlab.com/jangorecki/dockerfiles/r-devel https://gitlab.com/jangorecki/dockerfiles/-/raw/master/r-devel/Dockerfile On Sat, Jun 27, 2020 at 12:37 AM Jan Gorecki

>>>>> Kurt Hornik >>>>> on Tue, 30 Jun 2020 06:20:57 +0200 writes: >>>>> Jan Gorecki writes: >> Thank you both, You are absolutely correct that example >> should be minimal, so here it is. >> l = list(a=new.env(), b=new.env()) unique(l) >> Just for completeness, env_list during check that raises

Dear R developers, I spotted that R_isNA and R_IsNaN could be improved when applied on a vector where we could take out small part of their logic, run it once, and then reuse inside the loop. I setup tiny plain-C experiment. Taking R_IsNA, R_IsNaN from R's arithmetic.c, and building R_vIsNA and R_vIsNaN accordingly. For double input of size 1e9 (having some NA and NaN) I observed following

No packages are being loaded, or even installed. Did you try running the example on R-devel built with flags I have provided in this email? I checked now and it is required to use --enable-strict-barrier to reproduce the issue. On Tue, Jun 30, 2020 at 9:02 AM Martin Maechler <maechler at stat.math.ethz.ch> wrote: > > >>>>> Kurt Hornik > >>>>> on

Thank you Gabriel, Just for future readers. Below is a base R way to address this common problem, as instructed by you (+stopifnot to suppress print). Rscript -e 'stopifnot(file.copy("DESCRIPTION", file.path(tdir<-tempdir(), "PACKAGES"))); db<-available.packages(paste0("file://", tdir));

On 21 November 2019 at 17:57, Martin Maechler wrote: | (if you use a version of R-devel, with svn rev >= 77446; which | you may get as a binary for Windows in about one day; everyone | else needs to compile for the sources .. or wait a bit, maybe | also not much longer than one day, for a docker image) : FYI: rocker/drd [1] and rocker/r-devel both have rev 77455 now (as they are both on

Thank you Luke. That is why I don't use Rf_inherits but INHERITS which does not allocate, provided in the email body. I cannot do similarly for S4 classes, thus asking for some API for that. On Fri, Nov 1, 2019 at 5:56 PM Tierney, Luke <luke-tierney at uiowa.edu> wrote: > > On Fri, 1 Nov 2019, Jan Gorecki wrote: > > > Dear R developers, > > > > Motivated by

Dear R-devel, AsIs class seems to be well handled by `typeof` and `mode` function. Those two functions are being referred when explaining `is.vector` behaviour in manual. Yet `is.vector` does not seem to be handling AsIs class the same way. is.vector(1L) #[1] TRUE is.vector(I(1L)) #[1] FALSE Is there any reason behind this behaviour? Could we have it supported so AsIs class is ignored when

Dear Joris, So it does looks like the proposed function makes a lot sense then, isn't it? Cheers, Jan On 16 June 2016 at 08:37, Joris Meys <jorismeys at gmail.com> wrote: > Dear Jan, > > It is unavoidable to have OS and R dependencies for devtools. The building > process for packages is both OS and R dependent, so devtools has to be too > according to my understanding.

Hi all, Packages tools and utils have a lot of useful stuff for R developers. I find one task still not as straightforward as it could. Simply to extract dependencies of a package from DESCRIPTION file (before it is even installed to library). This would be valuable in automation of CI setup in a more meta-data driven way. The simple function below, I know it is short and simple, but having it to

Thank you Gabriel, Agree, although I think that could be relaxed in this single case and AsIs class could be ignored. Best, Jan On Sun, Mar 29, 2020 at 7:09 PM Gabriel Becker <gabembecker at gmail.com> wrote: > > Jan, > > I believe it's because it has "a non-NULL attribute other than names" as per the documentation. In this case its class of "AsIs". >

Hi R-devel community, I am aware of changes in R-devel in head/tail methods but I was not expecting that to be a breaking change. # R 3.6.1 ar = array(1:27, c(3,3,3)) tail(ar, 1) #[1] 27 The current output of R-devel is something that I would expect from a tail(ar, c(1, Inf, Inf)) or tail(ar, c(1, NA, NA)) calls. Is it going to stay like this or there are plans to mitigate this breaking

Hi Martin, Jan, On 11/03/2016 03:45 AM, Martin Maechler wrote: >>>>>> Jan Gorecki <J.Gorecki at wit.edu.pl> >>>>>> on Tue, 1 Nov 2016 22:51:28 +0000 writes: > > > Hello community/devs, Is there an option to run package > > tests during R CMD check and not stop on first error? I > > know that testing frameworks (testhat

Hello community/devs, Is there an option to run package tests during R CMD check and not stop on first error? I know that testing frameworks (testhat and others) can do that but asking about just R and base packages. Currently when package check runs test scripts in ./tests directory it will stop after first fail. Do you think it could be optionally available to continue to run tests after

Dear R developers, Motivated by discussion about checking inheritance of S3 and S4 objects (in head matrix/array topic) I would light to shed some light on a minor gap about that matter in R C API. Currently we are able to check inheritance for S3 class objects from C in a robust way (no allocation, thread safe). This is unfortunately not possible for S4 classes. I would kindly request new

Hi Michael, Are you willing to accept patch for this? I'm already using this and few related functions for a while, it plays well. I could wrap it as patch to utils, or tools? Best, Jan On 16 June 2016 at 14:00, Michael Lawrence <lawrence.michael at gene.com> wrote: > I agree that the utils package needs some improvements related to > this, and hope to make them eventually. This