Michael Müller
Michael Müller
@VadneyK Sorry for the late reply. I just tried building the contract from your `master` branch which works fine, for the tests there are some `insufficient funds` panics, but they...
> We might also find a lot of use for this technique in heavily used derive dependencies such as `parity-scale-codec`. That's a good point. And also a reminder of why...
@ascjones Do you have an idea if this will be fixed with https://github.com/paritytech/ink/pull/1243 ?
@forgetso It should all be on here: https://github.com/paritytech/ink/projects/8, the other one was an experiment which only existed for a short amount of time. I'm surprised that you even noticed it!
Ah I get it now, the link to the board was in the GitHub description of this issue, I've updated it. >Hi, can't wait to see cross contract testing. Yes,...
@frankli-dev You can use e.g. ``` info!( target: "runtime", "[ChainExtension]|call|func_id:{:}", func_id ); ``` inside your runtime. If you then run the node via `substrate-contracts-node --tmp --dev` it will show up...
@frankli-dev Have you tried starting without the `-l`? Maybe try panic-king in your custom chain extension in the runtime, just to verify that the function is even hit?
@johansten Did you already have a chance to look at the PR?
That's great to hear, thank you both!
@forgetso You're right that `--release` silences the output. Can you identify why your contract is so big? We observe that this typically happens because some third-party crate is included in...