-
Notifications
You must be signed in to change notification settings - Fork 158
chore(all): final small changes to the libevm branch #862
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
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.
lgtm
806247a
to
78d91ea
Compare
48c2b2e
to
7d06d0e
Compare
b9073f0
to
2c501ed
Compare
…izeAndAssemble Co-authored-by: Arran Schlosberg <519948+ARR4N@users.noreply.github.com> Signed-off-by: Quentin McGaw <quentin.mcgaw@gmail.com>
…n testBlockChain.CurrentBlock
… LegacyPool.startPeriodicFeeUpdate
…te test field in TestPredicateBytesExtra
This reverts commit c6072ff.
…multicoin balance Signed-off-by: Quentin McGaw <quentin.mcgaw@gmail.com>
1c6b47f
to
8b5354b
Compare
No-op force push due to a missing signature 🤷 |
Changes applied from comments on the review of ava-labs/coreth#820 See original PR ava-labs/coreth#862 Signed-off-by: Quentin McGaw <quentin.mcgaw@gmail.com> Co-authored-by: Arran Schlosberg <519948+ARR4N@users.noreply.github.com>
Even "no-op" force pushes can break other people's workflows. Just GPG-sign everything. By definition there can never be a completely no-op force push. While it may not change the file tree, it will change the commit history, and that's what GitHub relies on. If it was a no-op then a force push would be unnecessary. |
Changes applied from comments on the review of ava-labs/coreth#820 See original PR ava-labs/coreth#862 Signed-off-by: Quentin McGaw <quentin.mcgaw@gmail.com> Co-authored-by: Arran Schlosberg <519948+ARR4N@users.noreply.github.com>
Changes applied from comments on the review of ava-labs/coreth#820 See original PR ava-labs/coreth#862 Signed-off-by: Quentin McGaw <quentin.mcgaw@gmail.com> Co-authored-by: Arran Schlosberg <519948+ARR4N@users.noreply.github.com>
Why this should be merged
Final changes that will be squashed into the libevm branch, suggested from the PR review of #820
This also notably contains:
Let me know if you want me to split this PR, that's no problem as well.
How this works
revert
means the code is reverted to how it is on the master branch because the change is actually not needed.You can compare this branch to master here as well, for example to check on reversion changes.
How this was tested
Need to be documented?
Need to update RELEASES.md?