-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unanticipated behaviour change in rcmdcheck 1.3.0 #82
Comments
I can reproduce this. What the heck? |
Of course it does not happen when called from R, so debugging is a bit cumbersome.... |
It's default argument thing so we could say I was not careful enough. But I think you inserted two new ones near the front. This patch fixes it on my side: 1 file changed, 3 insertions(+), 1 deletion(-)
inst/examples/rcc.r | 4 +++-
modified inst/examples/rcc.r
@@ -58,8 +58,10 @@ if (requireNamespace("rcmdcheck", quietly=TRUE) == FALSE)
suppressMessages(library(rcmdcheck))
+rccwrapper <- function(pa, qu, ar, li, re) rcmdcheck(path=pa, quiet=qu, args=ar, libpath=li, repos=re)
+
sapply(opt$PATH, # iterate over arguments
- rcmdcheck, # calling 'rcmdcheck()' with arguments
+ rccwrapper, # calling 'rcmdcheck()' with arguments
opt$quiet, # quiet argument, default false
opt$args, # args arguments, possibly with --as-cran
opt$libpath, # libpath argument
[back] |
Oh, yes, sorry about that, some extra arguments were added in the middle of the argument list. So you'll have to name the arguments, I am afraid. |
Yes -- I do that now as per the diff I just applied. So do we call it mine then. Shall we close? |
Yes, I knew it was not a good idea to add them in the middle, but there seemed to be not too much rcmdcheck usage out there. And of course the reverse dependency checks do not apply to littler..... |
Well, there is not much I can do now, I am afraid. |
Especially not to littler examples as these are not functions... |
It is kinda funny that it ended up making HTTP requests.... |
Yep. A "WTF" moment here too. Also created a subdir |
I use
rcmdcheck()
quite a bit, mostly from a front-end scriptrcc.r
in littler that has not changed much in years.Below is a simple log showing that 1.3.0 changes behaviour over 1.2.1 and all prior versions. A simple check now wants to go off and do network access and what not.
The script does four simple things:
install.r
, another littler script wrappinginstall.packages()
rcc.r
on that same tarball, with successrcc.r
again on the earlier tarballand step four ends in tears.
The text was updated successfully, but these errors were encountered: