Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Just playing around, trying to restore all packages using
pak
. This usesrenv::restore
with the optionrenv.config.pak.enable=TRUE
.Locally, the pipeline builds in about 10 - 15 minutes (using 6 cores). In a github actions it cuts build time by half (from ~90 to ~45min)
RhpcBLASctl
packagescDblFinder
change the scores of some cells, voiding the snapshots)data.table::data.table
; harmony failing on too few cells in a subset test; some incorrectly stubbed functions)Due to the weird behaviours below, In Rstudio it might be better to not use pak to install the dependencies (using regular renv::restore installs quite quickly due to binaries available)
There are weird behaviours:
Installing packages locally (macOS) without fixing versions works. After snapshot, the lockfile can be restored using pak on a new and clean local Rstudio project. BUT fails in a docker container (rocker/r-ver) due to dependency conflicts.
The lockfile was generated by manually installing dependencies in a docker container and snapshotting from there (using
renv::snapshot(type = "all")
. This lockfile works in a docker container. But it brings issues on a local Rstudio project: it can be restored, but upon R restart, renv/pak return "subprocess could not start" errors when trying to install anything. The issue seems to be the lockfile, as renaming it to anything other than "renv.lock" (bypassing the automatic renv checks) fixes it, and allows regular package install using renv/pak.In addition, there's something broken with the .libPaths(), at least in my install, as some packages that are installed are not detected after re-starting R. They might be installed to a different library. But I don't have enough information yet.
for some reason, some bioconductor/github packages are installed twice (see the action log). renv/pak understand that they need to be updated, but it installs the same version number. Might be related to the remote used (bioconductor/github/RSPM)
Details
URL to issue
N/A
Link to staging deployment URL (or set N/A)
N/A
Links to any PRs or resources related to this PR
N/A
Integration test branch
master
Merge checklist
Your changes will be ready for merging after all of the steps below have been completed.
Code updates
Have best practices and ongoing refactors being observed in this PR
Manual/unit testing
Integration testing
You must check the box below to run integration tests on the latest commit on your PR branch.
Integration tests have to pass before the PR can be merged. Without checking the box, your PR
will not pass the required status checks for merging.
Documentation updates
Optional