Fix ic-wasm action failing on wrong version #2604
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
lmuntaner
approved these changes
Sep 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If
ic-wasmis 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--forcewe allow the script to continue an override the existing binary.