-
Notifications
You must be signed in to change notification settings - Fork 683
After calling evm_mine
, eth_getLogs
returns same logs for all blocks
#533
Comments
Any update on this? |
I've updated your comment to remove Ben, as he doesn't work on this project anymore. Thanks for taking the time to file this issue. I've added it to our queue of issues but don't currently have an ETA for the fix. |
Thanks for the heads up @davidmurdoch. |
We ran into this issue as well because of tests using |
We'll need to look into this. Don't like the sound of it! Thanks for reporting. |
I have a slightly different issue. I'm using I'm using Ganache 7.0.0 alpha2. |
@marmistrz-stc can you provide a reproduction script? |
Expected Behavior
eth_getLogs
should return the logs for the blockHash specified in the request.Current Behavior
After executing a
evm_mine
orevm_increaseTime
call to Ganache,eth_getLogs
always returns the logs for the latest block even if the request specifies a different blockHash.Possible Solution
Figure out what stateful change made during the
evm_mine
call is causing subsequenteth_getLogs
calls to ignore the suppliedblockHash
and always use the latest block.Steps to Reproduce (for bugs)
evm_mine
orevm_increaseTime
call with or without paramseth_getLogs
specifying any blockHash and you will always receive the logs from the latest block mined.Context
I am trying to write smart contract tests that check 0x order filling and expiration. I cannot cause orders to expire deterministically without use of
evm_mine
/evm_increaseTime
but cannot use it if it brickseth_getLogs
.Your Environment
The text was updated successfully, but these errors were encountered: