Fix build-deploy errors on push to main#5
Merged
Conversation
… to plain code fences so nothing executes during render
…o they render as inert code blocks instead of executing and failing on missing packages
…y lives in tutorials/
…tall R Packages' step
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sequential fixes were implemented to resolve failures in the GitHub Actions build-deploy workflow that runs on push to
main.Summary of fixes
Fixed the
R_LIBS_USERmismatch. TheVerify R Packages Installationstep was reading a differentR_LIBS_USERvalue than theInstall R Packagesstep. Packages were being installed into one library path, but later steps were looking in another. Therefore, R reported them as missing even though installation had succeeded. This was fixed by settingR_LIBS_USERonce at the job level, so every step shares the same value.Added missing system dependencies for
ubuntu-latest. The workflow runs on GitHub Actions’ current Ubuntu image, which does not includelibcurl4-openssl-devorlibuv1-devby default. Those headers are required to compile thecurlandfsR packages from source, so an explicitapt-get installstep was added for both. Background: GitHub Actions'ubuntu-latestrunner now uses Ubuntu 24.04 (Noble), which differs from previous Ubuntu runner images. Ubuntu 24.04 introduced thet64runtime library transition as part of the 64-bittime_tmigration along with other changes to the base system. As a result, development packages that may have been available implicitly on earlier runner images are no longer guaranteed to be present. Installinglibcurl4-openssl-devandlibuv1-devexplicitly ensures the development dependencies required to compile thecurlandfsR packages are available.Prevented
info_schema_tutorial.qmdfrom executing its code chunks. This tutorial callsbigrquery::bq_auth(), which requires Google credentials. The executable R/SQL chunks were converted to non-executing code blocks, so the tutorial still renders and remains copyable without trying to authenticate during site build.Removed a duplicate
info_schema_tutorial.qmdat the repository root. A duplicate copy outside thetutorials/folder was being rendered a second time, which reproduced the same failure independently of the change above. That stray duplicate was removed.Error logs
1. Mismatched R_LIBS_USER
2. Missing libcurl
3. Missing libuv
4. BigQuery authentication failure during render