`aggregate_verify` no longer accessible targetting `wasm32-unknown-unknown` about blst

[dot-asm]

Could you test #228? The omission was unintended...

[dot-asm]

Thanks! It doesn't sound like something I'd be willing to put together and maintain as GA test, too many moving parts... We do exercise wasi and emscripten builds, so it's not like wasm is in total darkness:-) And thanks for the report!

[emturner]

Hi, I've tested and can confirm that #228 does fix the issue!

[dot-asm]

Cool! I wonder if you could tell a little bit about your environment. Is it based on wasm-pack or something else? In the essence the underlying question is if there is a way to perform github actions tests in an wasm32-unkown-unknown environment, and if you have any ideas/pointers to share :-)

[emturner]

Of course! It's ultimately compiling into a wasm module, that gets linked against a custom module internally provided by our runtime. The code runs as the program in a tezos smart rollup, compiling against our SDK.

We don't use wasm pack or anything - very much just a plain cargo build --target wasm32-unknown-unknown.

We don't end up running any tests at all within a wasm32 environment, any unit tests all run natively (but we do run separate e2e tests against the full stack with the compiled module).

Hope that makes rough sense - happy to go into it more if you have any specific questions?