From f4a3980caec2c4b2b49bae92b5db235a1e0d7581 Mon Sep 17 00:00:00 2001 From: Frederik Rothenberger Date: Wed, 11 Sep 2024 13:21:32 +0200 Subject: [PATCH] Fix ic-wasm action failing on wrong version (#2604) If `ic-wasm` is not detected properly (this was encountered when caching actions became unreliable due to hitting the rate limit), then the bootstrap script attempts to install the right version. However, if cargo is not aware that a binary already exists, it will then fail. By using `--force` we allow the script to continue an override the existing binary. --- scripts/bootstrap | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scripts/bootstrap b/scripts/bootstrap index dda9c0ccc4..800b5d7424 100755 --- a/scripts/bootstrap +++ b/scripts/bootstrap @@ -26,7 +26,7 @@ echo "looking for ic-wasm 0.8.5" if [[ ! "$(command -v ic-wasm)" || "$(ic-wasm --version)" != "ic-wasm 0.8.5" ]] then echo "installing ic-wasm 0.8.5" - run cargo install ic-wasm --version 0.8.5 + run cargo install ic-wasm --version 0.8.5 --force fi # make sure the packages are actually installed (rustup waits for the first invoke to lazyload)