You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix: Emscripten config retains staging paths after catalog installation #246
Real WASM validation during kernal-api migration found the installed 4.0.21 package cannot pass its static health check: LLVM_ROOT and BINARYEN_ROOT in .emscripten still name the removed staging directory. install_spec writes config and optionally health-checks before renaming staging to its final package path, but does not relocate that config. Existing archive config tests only write directly to final paths and miss the lifecycle. Fix installation publication and existing managed installs without changing compiler version or JSPI defaults; add a staging-to-final regression and rerun real compiler health plus Blink compile. Refs #242 and forge-ci/kernal-api#205.
Implemented on the migration branch: final config is written before directory publication, and health checks refresh older managed configuration. Relocation regression RED then GREEN, invalid-config no-publication test passed, full Rust/Python checks and Clippy passed. The newly built CLI then passed real static and dynamic Emscripten health checks and compiled isolated Blink to valid static WASM. No compiler version or linker defaults changed. Included in PR #242.
archive::write_emscripten_config_at writes the config for the final install location while the package is still staged, and run_health_checks in install.rs rewrites the config of older managed installs before probing them.
The live managed install at ~/.fastled/toolchains/emscripten/linux/x86_64/4.0.21-5cd3cbe0316d/.emscripten names final paths, with zero occurrences of the staging directory:
Activity
zackees commentedon Sep 13, 2026
Implemented on the migration branch: final config is written before directory publication, and health checks refresh older managed configuration. Relocation regression RED then GREEN, invalid-config no-publication test passed, full Rust/Python checks and Clippy passed. The newly built CLI then passed real static and dynamic Emscripten health checks and compiled isolated Blink to valid static WASM. No compiler version or linker defaults changed. Included in PR #242.
fix: relocate Emscripten config before toolchain publication (refs #246)
fix: relocate Emscripten config before toolchain publication (refs #246)
zackees commentedon Sep 17, 2026
Verified on
main(4ebcabd):archive::write_emscripten_config_atwrites the config for the final install location while the package is still staged, andrun_health_checksininstall.rsrewrites the config of older managed installs before probing them.~/.fastled/toolchains/emscripten/linux/x86_64/4.0.21-5cd3cbe0316d/.emscriptennames final paths, with zero occurrences of the staging directory:fastled toolchain statusreportsactive state: healthy.--just-compile, strategy: cold), producingfastled_jsoutput.No compiler version or JSPI/linker defaults changed. Shipped in #242. Tracked in the burndown #262.