Gábor Csárdi
Gábor Csárdi
So maybe there is nothing to do here. Or maybe we could show the installation output from `00install.out`, still? Although it would be potentially difficult to decide when to do...
Signal interrupts are not propagated to worker nodes in background sessions with `parallel` clusters
> I believe the SIGINT signal is not propagated to the workers IDK if it is a good idea to propagate signals from the call subprocess recursively. Even if it...
Thanks! They are not intended to be used by other parties currently, hence they are also not documented.
Thanks! What are the pros and cons for this?
They are all running `R CMD check`, hence the name, but on a different set of platforms, so you'd only need to install one of them.
Why are you using all three of them? You really only need to use one of them. Nevertheless, these are only examples, so feel free to rename the workflows in...
Ah, right! Those are our tests for `r-lib/actions` itself. They are not for people to copy. We suggest that you copy the workflows from https://github.com/r-lib/actions/tree/v2/examples
I can't reproduce this, the test passes in the build pane, and also in an RStudio terminal. :( Can you check your config for potentially related env vars and options?
Yeah, same here. Same RStudio, R 4.3.2, no profile, no env vars, no test failure. The stack trace, otoh, looks pretty good, I might be able to work something out...
What's your theme? ``` > rstudioapi::getThemeInfo() $editor [1] "Chrome" $global [1] "Modern" $dark [1] FALSE $foreground [1] "rgb(0, 0, 0)" $background [1] "rgb(255, 255, 255)" ```