We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If cargo +nightly contract build is executed, the step [4/5] appears two times in the output:
cargo +nightly contract build
[4/5]
$ cargo +nightly contract build [1/5] Checking ink! linting rules Checking with toolchain `nightly-2022-03-14-x86_64-unknown-linux-gnu` Finished dev [unoptimized + debuginfo] target(s) in 0.10s [2/5] Building cargo project Updating crates.io index Finished release [optimized] target(s) in 1.45s [3/5] Post processing wasm file [4/5] Optimizing wasm file [4/5] Generating metadata Updating crates.io index Compiling metadata-gen v0.1.0 (/tmp/cargo-contract_VjAOjf/.ink/metadata_gen) Finished release [optimized] target(s) in 2.08s Running `target/ink/release/metadata-gen ''` [5/5] Generating bundle
It could just be a simple fix of using six steps instead, but I have a distant memory that the number of steps is dependent on the CLI flags used.
The text was updated successfully, but these errors were encountered:
build
Closed by #715.
Sorry, something went wrong.
No branches or pull requests
If
cargo +nightly contract build
is executed, the step[4/5]
appears two times in the output:It could just be a simple fix of using six steps instead, but I have a distant memory that the number of steps is dependent on the CLI flags used.
The text was updated successfully, but these errors were encountered: