[R-pkg-devel] devtools::check() endless loop

[Duncan Murdoch]

On 2025-12-09 10:02 a.m., Hüsing, Johannes via R-package-devel wrote:
> 
> -----Ursprüngliche Nachricht-----
> Von: Duncan Murdoch <murdoch.duncan using gmail.com>
> 
>> The next step is to fix all the errors and warnings (and some of the notes).  If >you need help with interpreting them, post them here.
> 
> 
> So far I managed to whittle it down zo 1 error, 2 warnings, and 3 notes.
> 
> Topics I may welcome some feedback on:
> 
> * R CMD check does not run from the command line (R does), this is not a biggie though, as R CMD check seems to be run as part of devtools::check()

Perhaps you are not building the package first, and then checking the 
built result?

If your package is named staduicc and you are working on version 1.0.0, 
there would be two steps.  The first step is

   R CMD build <path to>/staduicc

This produces staduicc_1.0.0.tar.gz .  The second step is

   R CMD check staduicc_1.0.0.tar.gz

This does the check.  The devtools::check() function does both of these 
steps.


> * "Checking for future timestamps" comes to a pause until a clock server is found but rejected for a lack of https protocol

I haven't seen that particular issue.  I think you probably just need to 
ignore it.
> * How do "Writing R Extensions" and R-pkgs.org relate? Seems to me the main difference is the reliance of r-pkgs.org on the usethis package. 

Writing R Extensions is the "official" documentation, written by the R 
Core group.  R-pkgs.org is a web site based on Hadley Wickham's book 
about R.  Hadley is not in R Core, but he has a lot of experience 
building packages, and works at Posit, a company that started building 
addons for R, and has now branched out.  He was the principal author of 
the devtools package.  usethis is another one of Posit's packages.  Its 
goal is to simplify the tasks that are required to work with R.

 >Speaking of this, does a usethis:: function exist which runs @examples 
in isolation from he other checks? The editor fails checking for matched 
brackets and stuff, so the example is the main debugging chore as I 
cannot seem to run examples without devtools::checking the rest.

You can check examples one at a time in an R session by running

   example( topic )

I don't know if there's an easy way to run all the examples but not run 
the rest of the checks.  I just run them all.
> * On a related note: browser() seems to be unavailable during running examples, correct?

Generally browser() will only work in an interactive session.  So if you 
had a call to browser() in an example, it would run when you used 
example(topic), but not when you used R CMD check.>
> *  As part of debtools::load_all() I get the Warning: replacing previous import 'dbplyr::sql' by 'dplyr::sql' when loading 'staduicc'. I did not invoke sql(). What am I to infer from this message?

I never use load_all(), so I can't really tell you anything specific 
about it.  My understanding is that it sort of fakes the process of 
building and installing a package.  I just build and install packages 
when I want to test them, in the belief that the time saved by 
load_all() comes with the risk that the fakery isn't perfect, and will 
waste lots of time when the real behaviour doesn't match the load_all() 
behaviour.

Duncan Murdoch