On 12/11/2018 8:32 AM, Duncan Murdoch wrote:
On 12/11/2018 8:09 AM, Thomas Lin Pedersen wrote:
I have a couple of packages (‘fiery’ and ‘reqres') that uses a mock of a rook
request for their examples. The mock is an R6 object containing a
rawConnection, along with a finalizer that closes this
On 12/11/2018 8:09 AM, Thomas Lin Pedersen wrote:
I have a couple of packages (‘fiery’ and ‘reqres') that uses a mock of a rook
request for their examples. The mock is an R6 object containing a
rawConnection, along with a finalizer that closes this connection when the
object is removed. So
On 12/11/2018 7:56 AM, Jared Knowles wrote:
Thank you so much for the help!
The origin of this mistake was mine - I forgot a ' following a # in my
roxygen example code - which meant roxygen ignored the closing parens on
the next line. (See example)
\donttest{
#' # You can also pass
I have a couple of packages (‘fiery’ and ‘reqres') that uses a mock of a rook
request for their examples. The mock is an R6 object containing a
rawConnection, along with a finalizer that closes this connection when the
object is removed. So far so good. I’ve recently been getting CRAN errors
Thank you so much for the help!
The origin of this mistake was mine - I forgot a ' following a # in my
roxygen example code - which meant roxygen ignored the closing parens on
the next line. (See example)
\donttest{
#' # You can also pass additional arguments to predictInterval through
REimpact
I cannot tell whether this will be helpful or not. It looks to me like the
warning occurs when one of your dependencies uses BiocInstaller. You could
create a database of all available packages
chooseCRANmirror()
chooseBioCmirror()
db = available.packages()
find the installation
On 11/11/2018 7:01 PM, Duncan Murdoch wrote:
On 11/11/2018 6:53 PM, Duncan Murdoch wrote:
On 11/11/2018 3:39 PM, Jared Knowles wrote:
Hi!
I have a bit of a weird issue when I'm trying to check my package merTools
(source repo available here: https://github.com/jknowles/merTools
On Windows
Thanks, fixed in R-devel and R-patched.
The problem was only in unserializing of raw vectors serialized in
ASCII, the format is not affected. Old serialized ASCII files created by
R 3.5 or earlier can be read in R-patched and re-saved in binary format,
which can in turn be read in R 3.5 and
