We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As discussed earlier, I run into a problem where the resolver hangs if there are too many repos.
repos
> pak::pkg_install('ATACseqQC', dependencies=TRUE) ✔ Updated metadata database: 5.50 MB in 13 files. ✔ Updating metadata database ... done ....................
Would there be a way to give some hint to pak to prevent the combinatorial explosion in the solver?
One way to reproduce is this container:
docker run --rm -it --env MY_UNIVERSE=https://bioc.r-universe.dev/ --entrypoint=R ghcr.io/r-universe-org/build-wasm:latest
You can also reproduce it with another container running ubuntu:24.04 and setting:
options(repos = c( binaries = "https://bioc.r-universe.dev/bin/linux/noble/4.4", universe = "https://bioc.r-universe.dev", CRAN = "https://p3m.dev/cran/__linux__/noble/latest", BioCsoft = "https://bioconductor.org/packages/3.20/bioc", BioCann = "https://bioconductor.org/packages/3.20/data/annotation", BioCexp = "https://bioconductor.org/packages/3.20/data/experiment", fallback = "https://cloud.r-project.org", archive = "https://cranhaven.r-universe.dev" ))
The text was updated successfully, but these errors were encountered:
I am probably hitting the same issue after adding a cranlike repo with many packages and trying to install a package with a medium to large dep tree.
It works when installing a package without or only a few deps.
There isn't any debug/verbose mode to narrow down what is happening inside the resolver, is it?
Sorry, something went wrong.
You can debug the R code as usual (debug(), browser(), etc.), and the the C code as usual, with gdb or lldb.
debug()
browser()
gdb
lldb
No branches or pull requests
As discussed earlier, I run into a problem where the resolver hangs if there are too many
repos
.Would there be a way to give some hint to pak to prevent the combinatorial explosion in the solver?
One way to reproduce is this container:
You can also reproduce it with another container running ubuntu:24.04 and setting:
The text was updated successfully, but these errors were encountered: