Site failed to build - Setup Package Cache

[RicCampbell]

Hello,
Not done anything else since last worked, made some small changes, added an episode, only other thing was I think it requested a RMarkdown update when creating a new RMarkdown file.

Site build failed under;
Setup Package Cache

 Subprocess backtrace:
   1. renv::restore(project = path, library = renv_lib, lockfile = renv_lock, …
   2. renv:::renv_restore_run_actions(project, diff, current, lockfile, rebuild)
   3. renv:::renv_install_impl(records)
   4. renv:::renv_install_staged(records)
   5. renv:::renv_install_default(records)
   6. local handler(package, renv_install_package(record))
   7. renv:::renv_install_package(record)
   8. base::withCallingHandlers(renv_install_package_impl(record), error = function(e)…
   9. renv:::renv_install_package_impl(record)
  10. renv:::r_cmd_install(package, path)
  11. renv:::r_exec_error(package, output, "install", status)
  12. renv:::abort(all)
  13. base::signalCondition(cnd)
  14. global (function (e) …
  Execution halted
  Error: Process completed with exit code 1.

should be viewable from repo https://github.com/RicCampbell/FAIR4RS_repos_dois

Cheers,

Ric

[tdjames1]

I'm not sure why it's falling to restore the renv in the build and deploy action.

Could you try making another small change and pushing to trigger the build again?

[tdjames1]

Hi @RicCampbell I'm now seeing the same error for this action for a repo that I created from the workbench-rmd template so it's definitely not a problem with anything you have done. I will investigate further and let you know.

[Robadob]

FYI this has happened before, I think it just resolved naturally. It's too deep in R land for me to understand the cause.

[tdjames1]

I managed to fix my repo with a patch that pulled in proposed changes to the renv from this PR (which has now been merged) on the template repo: carpentries/workbench-template-rmd#63

Other than just waiting for a natural resolution, I'm wondering what the best way to get this fixed up for @RicCampbell. Applying the update_packages.patch.txt that I used is probably the best option since trying to merge from the main branch of the template repo will cause conflicts.

@RicCampbell could you download and save the file that I linked (without opening in Notepad!) then navigate on the command line to the main working directory for your repo and try the following:

git apply --index path/to/update_packages.patch.txt
git add -u
git commit -m "Update renv"
git push

🤞

[RicCampbell]

Ah glad to know it's nothing I've done!
I tried a small commit and push, no luck I think.
Have done the patch, and I think this has worked! Little green tick of success is there!
Thanks all, hopefully this is the last issue I run into.

[RicCampbell]

Just as an extra @katefoneill also had this problem, but the patch seems to have worked there as well.