extraymond

Sometimes it's from a old cache from sccache(or cachepot), try unsetting and do a `cargo clean` works for me.

I think it might possible pallet-contract now takes a salt argument. And the integration test uses old pallet-contract code, which didn't have that as a option, also the polkadot-js api...

Some update on playing with the test case of issue666, I've tried different ways to generate salt and seems the one used by polkadot.js might be the culprit, I tried...

I've added a test repo against substrate-contract-node. https://github.com/extraymond/substrate-contracts-node/tree/solang-test-0.12.0/runtime All four types of salt value in the cross-contract calls test case can be executed without issues, which is really weird considering...

Some updates on my tests: For comparison, I've added ink/solidity cross contract tests, and the good news is that all 4 directions works regardless of how the salt is generated....

@seanyoung Thanks! I'm currently comparing solang's metadata generation behavior with cargo-contract ATM. What I found right now different between solang's metadata and cargo-metadata is in the `spec` field. It appears...

@athei @seanyoung Taking from the discussion above, can I summarize it into actions needed below? 1. `ink`: extract `ink-metadata` out of the metadata generation process of `cargo-contract` and expose inner...

Got it, let me continue on there and sync back once something clicks.

If someone is interested in building snap package to distribute armor. I got a snapcraft.yaml template working. For simplicity, I just dump the deb package so no compilation is required....

It would be nice to use smol in cloudflare worker! They landed socket support which impl AsyncRead/AsyncWrite. This enables connecting to tokio-postgres, which is pretty cool. https://github.com/cloudflare/workers-rs/blob/cfaabb5c021121a544c0981d05cf9317e4e03503/worker/src/socket.rs#L141 It would nice...