-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
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
Intermittent "not a valid binary" error during package install #655
Comments
Can you show a reproducible example and/or the full output of the installation? |
Of course! Here you go: This setup is from WSL, but I see the same happen on Docker hub build infrastructure. Adding DockerfileFROM rocker/rstudio:4.3.2
RUN R -e 'install.packages(c("pak","pkgdepends"), repos = "https://cloud.r-project.org")'
COPY stage_1_packages.txt /tmp/
RUN R -e "packages <- readLines('/tmp/stage_1_packages.txt'); pak::pak(packages); pak::cache_clean()" stage_1_packages.txt
Output
|
Can confirm also hitting this issue, can't build a docker image that used to build fine any more (last built it late 2023 but maybe 20-30 times in a month back then with no failures) - now I'm struggling to get any builds in Github Actions to succeed at all. |
I can't reproduce this, for me PPPM sends:
whereas in your output you get
which is clearly a different package file. So for you PPPM sends a source package instead of a binary package. This should not matter here, but it is easier and much faster to install pak from our repo, see https://pak.r-lib.org/reference/install.html#pre-built-binaries @danielloader Which platform? Which PPM repo? Which R package and what version? |
Dockerfile installs PAK as suggested:
R 4.2, CRAN or https://cloud.r-project.org, Reshape2 1.4.4.
Like @Jondeen - I'm seeing a decent failure rate, I'm just looping the docker build on my laptop with |
@danielloader That does not look like CRAN, looks like PPM. What's the output of this?
|
EDIT: never mind, this is something else. |
I believe that this was already fixed by dev pak (pkgcache) here: Latest pak release:
Dev pak:
If you use a pak nightly build from https://pak.r-lib.org/reference/install.html#nightly-builds then it should happen. |
Not to pester but is there likely to be a promotion of these nightly builds into a production build? Else I've got to update many dozens of dockerfiles to change the build step rather than just using latest stable. |
It should not happen any more with pak 0.8.0:
|
I'll just note that I am seeing the same problem when using Just in case this is helpful an example is installing the
The sources are: pak::meta_list("ps")[["sources"]]
# [[1]]
# [1] "https://cloud.r-project.org/src/contrib/ps_1.8.1.tar.gz" "https://cloud.r-project.org/src/contrib/Archive/ps/ps_1.8.1.tar.gz" The tar.gz seems to be just a source archive, but Directly running Thanks for the great package and sorry for not having a complete repro (I in no way insist on you investigating or fixing this soon, just hope it helps others with the same error message to maybe provide more info). I am using pak |
Update: I have a repro - it seems at least some old versions cause problems:
|
Hi,
I'm experiencing an intermittent error installing a packge using pak. It does not happen every time, but pretty close to 90% of the times I try.
The error seems to relate to #467 .
I'm building in a Docker file, and the package in question (
[email protected]
) does not install successfully, usingR4.3.2
and defaultinstall.packages('pak')
:The package is quite small, and I wonder if there could be a r/w race condition causing it. Installing it using
install.packages
works fine every time.Let me know if I can contribute with other details.
The text was updated successfully, but these errors were encountered: