-
Notifications
You must be signed in to change notification settings - Fork 775
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
Error: Rococo development wasm not available #6966
Comments
Hey, thanks for reporting this! Since fixes to templates should happen in the So far, it seems like your Where have you donwloaded/build it from? |
It does seem like that in the released polkadot binary, the development chain-specs such as rococo are not available:
|
Yes I was following the README in this repo and used the polkadot-aarch64-apple-darwin binary from the release. |
I see that the omni-node package is not enabling these features, which seems to be a mistake. Bit surprised about Polkadot -- quite likely we do the release builds with I can understand that we want the release binary to be lean, but at the same time it is a blow to the DX to not be able to use the released polkadot binaries for testing with ZN. I think we should one defacto testing relay chain spec in the binary, be it rococo or paseo. @brunopgalvao in the meantime though, you can edit the zombienet config to point to a rococo chain-spec json file path instead of the hardcoded one. cc @pepoviola |
I edited the zombienet.toml file like so: [relaychain]
default_command = "../polkadot-sdk/target/release/polkadot"
chain = "rococo-local"
chain_spec_path = "./rococo-local-plain.json"
[[relaychain.nodes]]
name = "alice"
validator = true
ws_port = 9944
[[relaychain.nodes]]
name = "bob"
validator = true
ws_port = 9955
[[parachains]]
id = 1000
[parachains.collator]
name = "charlie"
ws_port = 9988
command = "parachain-template-node" I now get the following error:
Do I need to manually generate and specify the parachain chain spec as well? Also, just to note, when I compile the
Notice how in the |
hey @brunopgalvao ! Not sure if your problem still persists, but the errors in the previous comment are most likely PATH related:
Can you ensure Also, I will investigate the initial reported issue in the meantime as well. |
Seems like aarch64 binaries are built with |
Do you suggest adding more features for the
The WASM binaries are present in the Linux |
# Description Seems like I added `SKIP_WASM_BUILD=1` 💀 for arch64 binaries, which results in various errors like: #6966. This PR unsets the variable. Closes #6966. ## Integration People who found workarounds as in #6966 can consume the fixed binaries again. ## Review Notes I introduced SKIP_WASM_BUILD=1 for some reason for aarch64 (probably to speed up testing) and forgot to remove it. It slipped through and interfered with `stable2412` release artifacts. Needs backporting to `stable2412` and then rebuilding/overwriting the aarch64 artifacts. --------- Signed-off-by: Iulian Barbu <[email protected]>
Thanks @iulianbarbu :) |
When I run:
according to the README in this repo, I get the following:
The text was updated successfully, but these errors were encountered: