Handle decoding multi-contract logs gracefully

[petertonysmith94]

Issue

When dealing with multi-contracts (see this), users might call ContractA, which calls ContractB.

ContractA will require an ABI, ContractB will not. So, if ContractB has some log() calls, those may bubble up to ContractA, which won't be able to decode them due to the lack of an ABI definition, and then we throw.

The issue is that the transaction may have been successful, in which case throwing an error can be confusing.

Original Discussion.

Potential solutions

These solutions are worth considering, but requires more in-depth thought to understand if it can cause other problems.

• We could print a warning instead of throwing an error when trying to decode ContractB logs as they come via ContractA. This approach could acknowledge the possible successful transaction while alerting the user to the decoding issue.

• Maybe the better approach would be to not throw it here, and just log a warning.

[petertonysmith94]

@arboleya I went with bug, but wasn't 💯, please change as you see fit 😄

[danielbate]

Was this resolved by #1936?

[petertonysmith94]

@danielbate yes - closed by #1936