-
Notifications
You must be signed in to change notification settings - Fork 3
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
Improved the debugging tools #1057
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jalextowle
requested review from
jrhea,
mcclurejt,
cashd and
sentilesdal
as code owners
June 13, 2024 19:01
jalextowle
force-pushed
the
jalextowle/debug/improved-etching-tools
branch
from
June 13, 2024 19:04
2ef6aa8
to
d7ec3e0
Compare
Pull Request Test Coverage Report for Build 9505286878Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9505329870Details
💛 - Coveralls |
Hyperdrive Gas Benchmark
This comment was automatically generated by workflow using github-action-benchmark. |
jalextowle
force-pushed
the
jalextowle/debug/improved-etching-tools
branch
from
June 13, 2024 19:42
fc72617
to
2284972
Compare
Pull Request Test Coverage Report for Build 9505740981Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9505783860Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9505908141Details
💛 - Coveralls |
jalextowle
force-pushed
the
jalextowle/debug/improved-etching-tools
branch
from
June 14, 2024 20:40
3212191
to
ddfeb66
Compare
jalextowle
force-pushed
the
jalextowle/debug/improved-etching-tools
branch
from
June 14, 2024 20:51
ddfeb66
to
67a57bc
Compare
Pull Request Test Coverage Report for Build 9522112274Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9522219255Details
💛 - Coveralls |
mcclurejt
approved these changes
Jun 14, 2024
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.
Awesome job! looking forward to using these
jalextowle
force-pushed
the
jalextowle/debug/improved-etching-tools
branch
from
June 14, 2024 21:23
5fb3485
to
7c5cdf6
Compare
Pull Request Test Coverage Report for Build 9522519186Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9522537306Details
💛 - Coveralls |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds a new mode to the debugging tools for simulating a transaction that has already been mined. This addresses a limitation of the tool by allowing users to simulate a transaction at a specified block height and transaction height within the block. This will make the tool more useful on mainnet and testnet environments where we can't assume that each transaction will be executed in separate blocks.
In addition to adding the new debugging mode, this PR also spruces up the tool and makes it more usable by relying more heavily on debugging-specific environment variables.
Review Checklists
Please check each item before approving the pull request. While going
through the checklist, it is recommended to leave comments on items that are
referenced in the checklist to make sure that they are reviewed. If there are
multiple reviewers, copy the checklists into sections titled
## [Reviewer Name]
.If the PR doesn't touch Solidity, the corresponding checklist can
be removed.
[[Reviewer Name]]
approve
calls useforceApprove
?transfer
calls usesafeTransfer
?transferFrom
calls usemsg.sender
as thefrom
address?token spend?
call
,delegatecall
,staticcall
,transfer
,send
)success
boolean checked to handle failed calls?delegatecall
, are there strict access controls on theaddresses that can be called? It shouldn't be possible to
delegatecall
arbitrary addresses, so the list of possible targets should either be
immutable or tightly controlled by an admin.
nonReentrant
?not a concern or how it's mitigated?
memory variables?
issues?
payable
functions restricted to avoid stuck ether?catch underflows?
Safe
functions are altered, are potential underflows andoverflows caught so that a failure flag can be thrown?
covering the full input space?