Apple Sillicon review debug session report
@avallecam is already working on this.
Since Jan 31, 2024.
Assessment
This issue has not been assessed yet.
Description
Hi 👋 I have been debugging the Apple Sillicon process for reviewing as a result of discussions in #104.
The summary: success is possible. 👍
Developer dependencies
These are the dependencies I had to install in my system (outside of R) - this may be helpful for the general contributing doc:
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"
brew install r harfbuzz fribidi libgit2 jpeg freetype libpng libtiff glpk
R dependencies
I wrestled with these a lot, because I kept getting errors around the renv_snapshot validation. I think this is the order in which it leads to success:
install.packages(c('RcppParallel', 'call', 'curl', 'httr', 'openssl', 'pkgbuild', 'rang', 'rstantools', 'xml2', 'desc', 'desc', 'pkgbuild', 'igraph', 'DiagrammeR'))
install.packages(c("sandpaper", "varnish", "pegboard", "tinkr"),
repos = c("https://carpentries.r-universe.dev/", getOption("repos")))
Followed by this, which should work immediately after the dependencies are available
renv::install() # might be optional
sandpaper::manage_deps()
The back and forth was not getting me anywhere for a while, receiving the same error for quite a while (see "Error" details below). When it ended up working I was sort of surprised. I spent 90 minutes to get this to work, from start on an Apple Sillicon device without any developer tooling. Part of that time was the back and forth, so I think we could reduce that somewhat by streamlining the steps.
Error
Error:
! in callr subprocess.
Caused by error in `renv_snapshot_validate_report(valid, prompt, force)`:
! aborting snapshot due to pre-flight validation failure
ℹ See `$stdout` and `$stderr` for standard output and error.
Type .Last.error to see the more details.
Next steps
I wrote this up in order to document the steps I took to resolve the installation process in a crude form. This helps the discussion about what to do with @avallecam. I am happy to add docs to the reviewer guidelines after seeing whether this is a reproducible solution.
- Dominant language
- R
- Stars
- 3
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from epiverse-trace/tutorials
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
epiverse-trace/tutorials#242 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
epiverse-trace/tutorials#241 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
epiverse-trace/tutorials#240 ·
-
priority
epiverse-trace/tutorials#234 · 1 assignee ·
-
epiverse-trace/tutorials#233 · 1 assignee ·
All issues in epiverse-trace/tutorials
Similar issues
-
documentation pkg infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
epiverse-trace/epiparameter#511 ·
-
function:write_dwc
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Urgent request: Due to vulnerabilities move to API version 12.6.1 (12.6.2 eventually) or 13.1.1 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
jbkunst/highcharter#849 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
r-lib/pkgdepends#485 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100