You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like the message is not able to be decoded. I don't particularly like the current flow of assuming that it can be decoded. Perhaps we can catch the UnicodeDecodeError and raise ContractLogicError with just the raw data. That might be the most constructive way to handle it.
fselmo
added a commit
to fselmo/web3.py
that referenced
this issue
Jun 8, 2023
- If we can't decode the revert reason string, simply raise the ``ContractLogicError`` with the raw data and issue a warning that there was an issue decoding a reason string.
- If we can't decode the revert reason string, simply raise the ``ContractLogicError`` with the raw data and issue a warning that there was an issue decoding a reason string.
pip freeze
outputWhat was wrong?
Function
raise_contract_logic_error_on_revert
raisesUnicodeDecodeError
when parsing receipt for the following responseresponse = {'error': {'code': -32015, 'data': 'Reverted 0xd27b44a9', 'message': 'VM execution error.'}, 'id': 3, 'jsonrpc': '2.0'}
The text was updated successfully, but these errors were encountered: