Find a better place for `check_contract` etc

[uint]

This came up in CosmWasm/cw-plus#755.

Currently there are a few utilities that live as examples in the cosmwasm-vm package - check_contract, module_size, multi_threaded_cache.

It would be nice to find a better place for them - they're not really examples. The most proper thing I can think of is to set up at least one new package (cosmwasm-toolbox? or separate packages?) that depends on cosmwasm_vm and put them there as binary crates - this way we can remove dev-dependencies like clap from cosmwasm_vm entirely.

[hashedone]

It can stay in examples for now to not affect every CI flow in the world, but I would strongly consider creating separate binary project for that and publish it as separate packages on crates.io (maybe with better names reflecting it being part of cw) so one can easily install it with cargo install cw-check-contract or so - I actually use check contract all the time to make sure contract is proper without uploading it to BC. I think that it is good starter issue, I think @jawoznia can take it.

[AbhinavMir]

The cw-toolbox idea is great. Currently working with CosmWasm and definitely see this as potentially important. Happy to solve this one, if no one's working on it already.

[jawoznia]

This is now stored under https://github.com/CosmWasm/cw-tools
It will also stay in examples of comswasm-vm for compatibility reasons.

https://crates.io/crates/cw-check-contract
https://crates.io/crates/cw-module-size
https://crates.io/crates/cw-multi-threaded-cache

[uint]

This is now stored under https://github.com/CosmWasm/cw-tools

Nice! Good job!

It will also stay in examples of comswasm-vm for compatibility reasons.

Do we have a deprecation plan? Should we add some sort of notice to the examples binaries? Like echo this to stderr:

`check_contract` will be removed from the next version of `cosmwasm-vm` - please use `cw-check-contract` instead.
> cargo install cw-check-contract

The next step would be to update places we check contracts from CI like these:

• cosmwasm
• cw-plus
• poe-contracts

[uint]

The cw-toolbox idea is great. Currently working with CosmWasm and definitely see this as potentially important. Happy to solve this one, if no one's working on it already.

@AbhinavMir Thanks for the interest! Jan was already working on this one, but we're happy for other contributions

[hashedone]

One thing to consider is to figure out the process (some CI check on cosmwasm-vm?) so we don't forget to update those binaries when cosmwasm-vm is updated. Ideas?

[uint]

One thing to consider is to figure out the process (some CI check on cosmwasm-vm?) so we don't forget to update those binaries when cosmwasm-vm is updated. Ideas?

The only thing that comes to mind is having the cosmwasm-vm binaries return an error code, but that's probably too drastic. Maybe a version later we'd do that?

[hashedone]

The problem is that we don't want to fail CI right after updating VM, as it would make it painfully to deliver anything. But does github allow for some notifications on release (like: keep in mind to update xxxx?). Or maybe we want to have something like dependabot running on cw-tools verifying the cosmwasm-vm version?

[webmaster128]

Can we make this a new package in this monorepo? If we move the binary to a different place, we will run into maintenance issue. Also cosmwasm-vm will include breaking changes from time to time in minor versions, as nobody really uses this crate except wasmvm and we want to keep versions in sync. So it's better if those things stay together.

multi_threaded_cache and module_size are examples and can stay there I think.

[hashedone]

We created the separate repo for this, but actually, I think you are right - we can move it here and it would solve issues. Probably as separate projects to package directory. It shouldn't be much work, can you handle it @jawoznia?

[webmaster128]

as separate projects

Why plural? It's only check_contract that matters, right?

[jawoznia]

Sure, I can handle it once I finish my current task.