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
Describe the bug
When an RPC Error: Internal JSON-RPC error occurs, the result of the message is displayed in the terminal.
In the current release, an error message is displayed in the terminal, but its data is not displayed.
There was a error message and error data in release 0.55.0.
creation of Test pending...
[vm]from: 0x5B3...eddC4to: Test.(constructor)value: 0 weidata: 0x608...056felogs: 0hash: 0x68a...063e4
creation of Test errored: Error occurred: revert.
revert
The transaction has been reverted to the initial state.
Error provided by the contract:
Stop
Parameters:
{
"0": {
"value": "1730229971"
}
}
You may want to cautiously increase the gas limit if the transaction went out of gas.
Result on 0.56.1
creation of Test pending...
creation of Test errored: execution reverted
@Aniket-Engg This actually happens when a transaction was sending (like on Remix VM). However, if the transaction is canceled, the error data is not written in the terminal. Try to connect the metamask, deploy the contract and cancel the transaction.
creation of Test pending...
creation of Test errored: Error occurred: execution reverted.
execution reverted
The transaction has been reverted to the initial state.
Error provided by the contract:
Stop
Parameters:
{
"0": {
"value": "1730290540"
}
}
You may want to cautiously increase the gas limit if the transaction went out of gas.
Describe the bug
When an
RPC Error: Internal JSON-RPC error
occurs, the result of the message is displayed in the terminal.In the current release, an error message is displayed in the terminal, but its data is not displayed.
There was a error message and error data in release 0.55.0.
To Reproduce
Steps to reproduce the behavior:
Result on 0.55.0
Result on 0.56.1
Desktop:
Remix 0.56.1 (and 0.57.0-dev) on https://remix.ethereum.org/
The text was updated successfully, but these errors were encountered: