Open TyceHerrman opened 2 years ago
Tried disabling wasm-opt as suggested in the original error message, but was unsuccessful (don't really know how to use Cargo.toml). First tried adding wasm-opt = false
, then tried adding
[package.metadata.wasm-pack.profile.release] wasm-opt = false
to Cargo.toml in my local repo cloned from Matico repo (the second Cargo.toml edit based on https://rustwasm.github.io/docs/wasm-pack/cargo-toml-configuration.html).
Both attempts to no avail - same error for the first attempt, and the second attempt produced the following:
[rust-builder 20/31] RUN cargo build --release:
0 0.215 error: failed to parse manifest at
/app/Cargo.toml
0 0.215
0 0.215 Caused by:
0 0.215 missing field
name
for keypackage
failed to solve: executor failed running [/bin/sh -c cargo build --release]: exit code: 101 `
Hey @TyceHerrman Thanks for the bug report. I unfortunately don't have an M1 mac to reproduce this but @nofurtherinformation does. He is away on holiday for a little bit but when he gets back I can ask him to take a look at this.
We are revamping the way we do builds this week. There is a good chance the tweaks will fix this problem. Will ping you when it's merged to give it a go.
Tried this again today and am now getting the same issue as #148. Found this https://stackoverflow.com/questions/72061535/getting-this-error-message-while-installing-solana-error-failed-to-run-custom, which after completing the steps described, allowed me to run first step of individual components (cd matico_spec; cargo build; wasm-pack build --scope maticoapp)
, which had been failing previous to following the steps linked above. Still failed at (cd matico_charts; yarn build)
- see #151.
While using the docker-compose up environment setup, I receive the following warning (not sure if it's relevant) and error on my m1 mac:
This seems to be related to this issue with wasm-pack: https://github.com/rustwasm/wasm-pack/issues/913.
It looks like it was addressed in wasm-pack v0.10.2: https://github.com/rustwasm/wasm-pack/releases/tag/v0.10.2
I'm not able to definitively determine which version of wasm-pack Matico is using, but it looks like in the Dockerfile that it's pulling the latest version from the wasm-pack github repo (I could be misinterpreting that though). If that's the case, not sure why this error would occur.