Gherman

@cmichi After some digging around: we can use `quickcheck( as )` directly in our E2E tests as shown [here](https://github.com/BurntSushi/quickcheck#shrinking). It behaves exactly as macros. However, that would require "diving" into...

Can we also investigate why the CI was hanging on a single running instance? AFAIK it works just fine locally

ink! is intended to be as close to idiomatic rust as possible. If this behaviour is "normal" in classic rust, I don't see a reason why we should be concerned...

I believe we need to address https://github.com/paritytech/ink/issues/1388 first

Sure @deepto98 Feel free to tackle the issue. `encode` function has been added so you shouldn’t have any problem getting this to work. Thanks!

`suri` is used for `CallDryRun`: https://github.com/paritytech/cargo-contract/blob/aa97589725ef15ef591182e294acc7e0797387e2/crates/cargo-contract/src/cmd/extrinsics/call.rs#L180

Since we are modifying files with cargo, docker process and user must be in the same Linux group. Have you done [docker post-installation steps?](https://docs.docker.com/engine/install/linux-postinstall/)

Are you running as a user with sudo privileges?

This is an issue related to the contracts-ui

Are you using `substrate-contracts-node`? If so, what version is it. We also released ink! 4 release candidate which you should use now.