Juniper Tyree

LGTM, thanks for adding the fix and the test so quickly!

Does the error persist with `-Zbuild-std=std` or perhaps even `-Zbuild-std=std,compiler-builtins`

Zstandard and SZ3 are implemented in C(++) and haven't changed in the meantime, so Rust compilation wouldn't affect them. The Rust wrappers just forward values, so only the WASM boundary...

I made some progress with `pyarrow`. I think the problem is that, while previously we would just look for shared libraries inside the wheel, now we no longer do. `libarrow_python.so`...

But of course, now we get to the real fun runtime link-errors: If I try to import my new `pyarrow` package, it loads the shared libraries in directory order, which...

I tried with `healpy` as well and that requires an even worse post build: ```yaml post: | cp ${WASM_LIBRARY_DIR}/../healpy/build/healpy-1.18.1/build/temp.emscripten_4_0_9_wasm32-cpython-313/lib/libcfitsio.so ${WASM_LIBRARY_DIR}/lib cp ${WASM_LIBRARY_DIR}/../healpy/build/healpy-1.18.1/build/temp.emscripten_4_0_9_wasm32-cpython-313/lib/libhealpix_cxx.so ${WASM_LIBRARY_DIR}/lib cp ${WASM_LIBRARY_DIR}/../healpy/build/healpy-1.18.1/build/temp.emscripten_4_0_9_wasm32-cpython-313/lib/libsharp.so ${WASM_LIBRARY_DIR}/lib ``` Since this wasn't...

My commit with these changes is https://github.com/climet-eu/pyodide-recipes/commit/65149b56632e3e6782bda12da55b912cbb06930b

> > has some wonderful comments about loading the shared libraries in the correct order ... and does nothing of the sort. I guess the shared libraries should be topologically...

I made some progress on healpy. In the end, setting exports: requested was needed to expose the missing symbols. For some reason that caused test binaries to fail to compile,...

I've also noticed that switching workspaces doesn't work on my deployment. It seems to strip the `index.html` from the URL, which is needed.