-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: unexpected zero gas_consumed
#412
Comments
@xJonathanLEI with #429 on latest mainnet it now gives:
But of course this now on a different block, and I cannot find the block you executed this on. Could you specify block hash and the network just in case if this doesn't look more correct? Let's keep this issue open until you've confirmed regardless of how #429 progresses. |
@koivunej My fault making the script non-deterministic. I've updated the script to use a block hash instead (response updated too). |
BTW my script was actually running against |
Oki I don't have the goerli snapshot at hand right now... Maybe you can test the PR branch directly or let us know how it looks later after merge? Feel free to close if this is okay approach. It will be disputable if the floor or ceil operation on coercing the gas_consumed to integer over at python side is correct, or maybe it should be rounded. I went with floor/truncation for now, assuming that's what python does with |
No worries I have a mainnet node too :) Script and response updated again for |
Oki finally checked the latest version, the 0x29 gas used is the same from earlier testing:
Closing for now, feel free to ping/reopen. |
Description
When calling
starknet_estimateGas
, thegas_consumed
field returned in zero.Steps to reproduce
Run this script:
Note: as of this writing the hosted node is running
v0.2.3-alpha
Expected result
The field
gas_consumed
should be non-zero since the two other fields are also non-zero.Actual result
The text was updated successfully, but these errors were encountered: