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
{{ message }}
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.
By default, contracts using autoGas should multiply the gas estimate by 1.25. At the moment, the multiplying logic seems like it just returns the original estimate value.
Web3 1.2.2 fixes long-broken logic that registers a transaction as failed when the gas consumed equals the gas sent. In older versions of the eth chain and some contemporary forks ( ETC? maybe Quorum?) failing txs consume all gas and the gas comparison is a reliable indicator that something has gone wrong.
This is relevant for #2488 because truffle-contract's tests are fueling the tx's with perfect estimates and triggering a false error.
The question of what behavior is correct is a little complicated and will need further discussion at Web3, but Truffle could side-step this by fixing the multiplier.
Issue
By default, contracts using autoGas should multiply the gas estimate by 1.25. At the moment, the multiplying logic seems like it just returns the original estimate value.
Web3 1.2.2 fixes long-broken logic that registers a transaction as failed when the gas consumed equals the gas sent. In older versions of the eth chain and some contemporary forks ( ETC? maybe Quorum?) failing txs consume all gas and the gas comparison is a reliable indicator that something has gone wrong.
This is relevant for #2488 because truffle-contract's tests are fueling the tx's with perfect estimates and triggering a false error.
The question of what behavior is correct is a little complicated and will need further discussion at Web3, but Truffle could side-step this by fixing the multiplier.
Possible that #2512 is related...
cf: web3 3175
Steps to Reproduce
Environment
truffle version
): 5.0.41node --version
):npm --version
):The text was updated successfully, but these errors were encountered: