Final approval of utility as_multi leads to error in events

[philipstanislaus]

I'm playing around with multisigs right now, but when I do the final approval, I see this error in the events:

Uncaught error. Something went wrong with the data extraction, resulting in an error log.

Steps to reproduce:

1. Run: docker run -p 9933:9933 -p 9944:9944 -p 30333:30333 parity/substrate:2.0.0-14720148 --ws-external --rpc-external --dev
2. Submit the first multisig extrinsic:

3. Inspect the events to find the AccountId of the "2 of Alice, Bob" multisig by inspecting the events, here `5F3QVb...MCh4Ch`:

4. Send funds to that AccountId:

5. Submit the second (final) multisig extrinsic:

6. Find the error in the logs:

Many thanks for helping resolving this!

[jacogr]

Brilliant! Thanks for the detailed report. This could very well be related to having an old implementation of DispatchError where the UI currently only supports the latest.

Will however follow along and attempt it on a current Substrate master.

Ummm... ok, looking at your screenshots again, it is on 204 (latest substrate), so def an issue.

[jacogr]

Just one question - do you have overrides for DispatchError in your types?

[philipstanislaus]

No, I’m actually running the substrate default node and the deployed Polkadot Apps (no overrides in the settings either).

Thanks for the blazing fast turnaround! 🚀

[jacogr]

So 2 issues here -

1. The actual Error metadata for utility is not exposed, this is fixed here - Expose Error in metadata for pallet-utility paritytech/substrate#4721
2. When finding non-existent (as above), the UI will now fallback to displaying the module/error struct (aka allow for manual lookup, instead of just displaying nothing) - Handle DispatchError failures gracefully #2182

[philipstanislaus]

Awesome, thanks!

[polkadot-js-bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.