rwasmbuild errors

[jgeller112]

Hi @coatless!

I am using your GA code to build my package website with webr.
I am not sure what is going on now, but my I am now encountering some issues with my build (worked before). See error below:

Adding packages:
* .
Processing 1 package(s).
! Using bundled GitHub PAT. Please add your own PAT using `gitcreds::gitcreds_set()`.

v Updated metadata database: 2.33 MB in 2 files.

i Updating metadata database
v Updating metadata database ... done

i Scanning dependencies in '_site/src/contrib/webgazeR_0.7.2.tar.gz'
v Scanning dependencies in '_site/src/contrib/webgazeR_0.7.2.tar.gz' ... done


 
 
> The package (0 B) is cached.
  
i No downloads are needed
v :  [343ms]
ERROR: dependencies 'tidyverse', 'janitor', 'readxl', 'ggokabeito', 'here', 'knitr', 'tinytable', 'easystats', 'zoo' are not available for package 'webgazeR'
* removing '/tmp/RtmpgCSTlA/file12290de43/webgazeR'
Processing packages:
  /github/workspace/_site/src/contrib/webgazeR_0.7.2.tar.gz
done
There were 26 warnings (use warnings() to see them)


Making library
Packaging: library.data
Error in file_packager(lib_abs, out_dir, out_name = out_name, compress) : 
  An error occurred running `file_packager`:
Remember to build the main file with `-sFORCE_FILESYSTEM` so that it includes support for loading this file package
Nothing to do!
Calls: <Anonymous> -> file_packager
In addition: Warning message:
In system2(file_packager, args = c(data_file, "--preload", sprintf("'%s@/'",  :
  running command ''/opt/emsdk/upstream/emscripten/tools/file_packager' library.data --preload '/tmp/RtmpgCSTlA/file17e7bddfd@/' --separate-metadata --js-output='library.js' 2>&1' had status 1 and error message 'Function not implemented'
Execution halted
Ran 2/2 deferred expressions
Error: Process completed with exit code 1.

Any ideas what could be wrong?

Thanks for any insight.

[coatless]

@jgeller112 new version of webR v0.5.2 is out about ~3 weeks back. As this is throwing errors on dependencies, maybe the existing webR repo (https://repo.r-wasm.org) is no longer serving them or the redirect became problematic?

If I recall, the GitHub Action with the R WASM build process was tagged to 0.4.2

quarto-webr-in-altdoc/.github/workflows/altdoc.yaml

Line 34 in bdba429

webr-image: "ghcr.io/r-wasm/webr:v0.4.2"

The {quarto-webr} version is tagged to 0.4.0 (no major differences in packaging between the two).

https://github.com/coatless/quarto-webr/blob/8ad65f045e718ecfd45c0e5b2ec04998dd508c0f/_extensions/webr/webr.lua#L18

So, possible this is just a requirement to bump up to webR 0.5.2.

[jgeller112]

No lucky, sadly.

[coatless]

Need to bump {quarto-webr} up to v0.4.3.

Add to GitHub Action workflow:

quarto-webr-in-altdoc/.github/workflows/altdoc.yaml

Lines 76 to 82 in 6961242

	# Tagged quarto extension versions to work with webR ---
	- name: Grab tagged versions of Quarto Extensions
	run: |
	cd altdoc
	quarto add --no-prompt coatless/quarto-webr@0.4.3
	quarto add --no-prompt coatless-quarto/panelize@0.0.2
	cd ../

[jgeller112]

Here is my yml: https://github.com/jgeller112/webgazeR/blob/master/.github/workflows/altdoc.yaml. I dont think that is the issue. It is happening during the build of rwasm. I could be mistaken.

[jgeller112]

Very weird because this has been working for a while. I am not sure what happened.

[coatless]

@jgeller112 I think this might be more on the repo.r-wasm.org end where packages are obtained from. I can't look more now.

[jgeller112]

Bummer! Thanks for helping. I will get rid of webr for now.

[jgeller112]

Do you know who I should reach out to to see if there is a solution. I really want to keep webr.