-
Notifications
You must be signed in to change notification settings - Fork 202
Collect EVM-related events during VM bridge bootstrapping #7999
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
2169c9d to
7de2383
Compare
Kay-Zee
left a comment
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.
Great! Looks like the main difference is changing from run to runAndReturn, which also completely removes the run function, which had previously used invokeMetaTransaction and now just use runMetaTransaction, I believe the main thing here is that the events are returned, were there any other side effects to this change?
Hey @Kay-Zee , so invokeMetaTransaction is just a wrapper around You are right, the main reason to use The only other issue I had to fix, was setting a proper transaction index, for each transaction that was executed as part of the VM bridge bootstrap, as the order to Other than that, I didn't notice any side effects. |
|
Alright, LGTM! |
janezpodhostnik
left a comment
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.
Nice!
Only had one minor comment.
@janezpodhostnik There doesn't seem to be any written comments 😅 |
fvm/bootstrap.go
Outdated
| panic(fmt.Sprintf("failed to build pause the bridge contracts transaction: %s", err)) | ||
| } | ||
| run(txBody, "failed to pause the bridge contracts: %s") | ||
| runAndReturn(txBody, "failed to pause the bridge contracts: %s") |
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.
if we don't need run anymore can we rename runAndReturn to run
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.
Good point 👍 Renamed it in 46df27c .
|
Sorry about that. Added it now. |
7de2383 to
46df27c
Compare
Work Towards: onflow/flow-evm-gateway#893