Note that by calling py_module_available() in your .onLoad(), as done here:
https://github.com/r-cas/caracas/blob/418b3a552de0203c3d2f960f0e4235f7891db71d/R/init.R#L51
you are forcing reticulate to initialize the Python session eagerly
when your package is loaded (so before the user might've had
Hi list members,
On checking the CRAN Package Check Results for my package growthPheno I find
that there is the error below for r-devel-windows-ix86+x86_64, but not for
r-devel-windows-ix86+x86_64-gcc8. Further, I do not get this error when I run R
CMD check --as-cran on the tarball for a new v
Hi Berry,
Thank you for the note.
When I run my example code with transparent_color() all was working (the
color was transparent).
Now, reproducing the code again it becomes black. Could be this be changed
after package "farver" be updated to v. 2.0.2?
You is right regarding the use of col = N
Side Note:
plot(1, col="#00FF", cex=4, pch=16)
is black on my machine.
The last two values are alpha (I think) and should be 00 for transparency.
Instead of writing an extra function, you could also use col=NA.
Berry
From: R-package-devel on behalf of
Hi Joris,
Thank you for your suggestions.
After installing the version v 2.0.2 of "farver" I was able to reproduce the
WARNING.
To fix this issue, I created a simple helper function:
transparent_color <- function() {
return("#00FF")
}
And changed "transparent" with "transparent_color()" in my
Hi Tiago,
It's indeed that. For some reason col2rgb() knows the unofficial "transparent".
Replace this with the correct value from the vector colors(), i.e. "white".
"transparent" is not mentioned in that vector, so it shouldn't be used in a
package. See also ?rgb2col and ?colors.
Cheers
Joris
Hi Tiago,
Then it seems likely that an update of a direct or indirect dependency
of your package causes this failure on CRAN's check system.
ggplot2 currently fails with a similar error message on CRAN
> Error: Unknown colour name: NA
(https://cran.r-project.org/web/checks/check_results_ggplot2
Hi Joris,
Thank you so much for your assistance.
I've built and checked my package with:
R CMD build /d/Desktop/metan
R CMD check --as-cran metan_1.2.1.tar.gz
No WARNINGS were observed. Please, see the log file attached.
Sorry for failing in providing the link to access the check results in the
la
Hi Tiago,
Without knowing which package you're talking about or a link to the check
results, it's impossible to know whether that warning is a proper one or a side
effect of something else.
In general though: it is well known that relying on devtools is not enough for
a good CRAN submission.
I wonder why does vignettes/checkpoint.Rmd run the following:
> example_project <- tempdir()
Now example_project contains the path of per-session temporary
directory...
> dir.create(example_project, recursive = TRUE, showWarnings = FALSE)
...so there should be no need to create it...
> unlink(
Dear all,
In the last submission of my package the CRAN team has suggested including
some references in the description field of the DESCRIPTION file.
When I submitted it to CRAN it did not pass the incoming checks
automatically and I got the following WARNING.
Quitting from lines 108-117 (vig
I finally got this to work by removing the Config part of DESCRIPTION
and reverting back to functionality inside .onLoad(). Please see code
that does not trigger any warnings/errors here:
https://github.com/r-cas/caracas/tree/418b3a552de0203c3d2f960f0e4235f7891db71d
Cheers,
Mikkel.
tor, 09 01 20
12 matches
Mail list logo
