-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: UnknownError: Command failed with ENOENT #222
Comments
upon initial inspection of the https://docs.astar.network/docs/build/wasm/swanky-suite/cli/, it says that "swanky-cli, as well as environment in the swanky-base image, and supported tools target ink! v4, and use cargo contract v2". it also says here https://docs.astar.network/docs/build/wasm/swanky-suite/node#compatible-ink-version that only ink! 4.0.0 is supported. it also says here https://docs.astar.network/docs/build/environment/ink_environment/#rust-and-cargo that due to a bug in cargo-contract, building contracts with rust nightly 1.70.0 or higher will fail. It is advised to use rustc v1.69.0 or older until the issue is resolved from cargo-contract side currently i'm running
so to be able to use swanky-cli (instead of cargo contracts node and the latest versions shown above), it's necessary to downgrade to:
|
so i reverted to the older versions by running the following
note: it was necessary to use i then modified the wasm-flipper Cargo.toml file to use ink! 4.0.0 as shown below
then ran cd dapps/ink-rust
nvm install
nvm use
yarn global add @astar-network/[email protected]
cd ./wasm-flipper/contract/flipper
swanky node start but i still got the error
|
if i run swanky node install
swanky node start it shows better errors including:
|
What happened?
When create a new flipper template using https://github.com/ltfschoen/XCMTemplate by following these steps in the README after following the steps to run it in Docker https://github.com/ltfschoen/XCMTemplate?tab=readme-ov-file#build--upload-ink-rust-flipper-smart-contract-to-local-testnet-using-swanky-cli-, when I run
yarn && yarn run run-node
orswanky node start
it outputsOr if i run
swanky node start --tmp --verbose
it outputsSteps to reproduce
yarn && yarn run run-node
orswanky node start
Expected behavior
it should start the swanky node instead of generating that error
Actual behavior
it generates error:
Environment
rustup show
)node --version
)Note: I get the same error even if i switch to Node.js v18.20.2
Logs, Errors, Screenshots
Additional information
No response
The text was updated successfully, but these errors were encountered: