Tool extraction failure about perseus HOT 8 CLOSED

thank you! that fixed it. Fixed by running:

perseus serve -w --wasm-opt-version version_110

subsequent runs work without the flag:

perseus serve -w

from perseus.

Hmm, that's extremely weird. What's your OS?

from perseus.

@arctic-hen7 Ubuntu 22.04, also worth mentioning (thought I posted with issue) i'm on perseus 0.4 beta

This wasn't happening before, just started happening, which is what led me to try generating a new app

It sounds like a file perm error, where is wasm-opt being axtracted to?

from perseus.

Hmm, same. It's extracted to your system cache directory, which should be something like ~/.cache/perseus-cli/tools for you. Could you try clearing that directory? Perseus should use the local dist/ directory if it finds the systemwide cache unusable, which implies that this might have been caused by a corruption of some sort. I've experienced some weird Cargo failures causing tool reinstallation in the past, so it could be something like that.

from perseus.

UPDATE: This is now occurring on CI, so I think this might be a critical bug that's worked its way into the installation process somehow.

from perseus.

Okay, this has been caused by the wasm-opt team releasing a new version without including any release artifacts. The CLI defaults to the latest version, and it can't find the artifacts, hence the problem! Add --wasm-opt-version version_110 to the first Perseus command you run, and everything will work perfectly. (You won't need to add this flag again.)

from perseus.

See WebAssembly/binaryen#5282.

from perseus.

The artifacts for wasm-opt's parent package have now been released for v111, so this problem should no longer affect anyone! I'll leave this issue open until the upstream one is definitely closed, and then I'll remove the warning in the README.

from perseus.