Conversation
We try to get the more information for failed transaction and output it instead of just throwing a TransactionFailed exception
|
I tried to write a test for this, but eth_tester and a real chain doesn't seem to behave the same way. When a transaction fails in eth_tester we actually get the revert reason: because eth_tester tries to get it for us. Also what I notice is that in the tests get_transaction returns a dict with a data prop, but in real life we get an input prop: @cducrest - any ideas, or should we just ignore? |
|
Looks fine, you should update web3 to the same requirements in the contracts and relay though. Otherwise if we need a new feature of the contract-deploy-tools there, we may not be able to use it before additional dependency work. (also fix mypy) |
I was failing to transact with a contract and the "TransactionFailure" exception was not particularly helpful.
It turns out that the latest web3 version has the ability to output the revert reason so, we are now trying to get it before raising a "TransactionFailure" exception.