-
Notifications
You must be signed in to change notification settings - Fork 335
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
Refactor evm recursion lock #2433
Conversation
Coverage generated "Mon Aug 14 14:56:41 UTC 2023": Master coverage: 87.39% |
What was the point of the refactor? Changes, FYI: moonbeam-foundation/frontier@ee898e9 |
Fix a race condition bug that occur randomly in ts tests (can occur only in native mode), for more details, see MOON-2209 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked the frontier commit moonbeam-foundation/frontier@ee898e9
The main change here seems to be deferring the Edit: It seems like it shouldn't, this is just using a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved. The new code seems good to me, but I'm not sure about the old code -- do you know why it was previously failing sometimes?
@librelois can you merge this one? |
What does it do?
Refactor evm recursion lock to avoid race conditions (may happen only in native mode, but ti's problematic for tests)
What important points reviewers should know?
Is there something left for follow-up PRs?
What alternative implementations were considered?
Are there relevant PRs or issues in other repositories (Substrate, Polkadot, Frontier, Cumulus)?
What value does it bring to the blockchain users?