Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

evm_mine and miner_start don't respect --mode.instamine=eager #2029

Open
davidmurdoch opened this issue Jan 10, 2022 · 4 comments
Open

evm_mine and miner_start don't respect --mode.instamine=eager #2029

davidmurdoch opened this issue Jan 10, 2022 · 4 comments

Comments

@davidmurdoch
Copy link
Member

evm_mine and miner_start shouldn't return until all the blocks have been mined, but they do. Additionally, we need to figure out how to handle subscription timings (newHeads, etc); should they be sent after all blocks have been mined (and thus always after the RPCs complete their return), or after each block?

@msuscens
Copy link

msuscens commented May 2, 2022

👍 I suspect this issue breaks the ganache-time-traveller library - which means I'm unable to use Ganache v7 with the project I'm developing as all my truffle tests extensively use TimeTraveller (my tests work fine with Ganache 6).

@davidmurdoch
Copy link
Member Author

@msuscens, I believe this was mostly fixed in c32aee8, but we've since discovered a race condition that can cause some issues. We have a PR in progress to solve this race condition here: #3016

@MicaiahReid
Copy link
Contributor

@davidmurdoch, #3016 should have fixed this. I can add tests to make sure of this.

In terms of subscription timings, we fire those off as they are ready rather than waiting for all blocks to be mined. Do you think that's a problem? I don't think we know what the preferred behavior would be, I'd vote not to hold up this issue and to leave as is. Maybe we could also put up a poll in the GitHub Discussions for what the expected behavior would be?

@msuscens
Copy link

msuscens commented Jun 21, 2022

@msuscens, I believe this was mostly fixed in c32aee8, but we've since discovered a race condition that can cause some issues. We have a PR in progress to solve this race condition here: #3016

@davidmurdoch I've tried again under v7.3.1 but I still get the same issue when advancing time: I've described the issue in full here: #3264

Is being unable to correctly advance time being caused by this issue? Or is it another issue - in which case shall I create a new issue (from my discussion post)?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Status: Backlog
Development

No branches or pull requests

3 participants