feat: print call trees on error #292
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
this way is more robust
move more data into TraceFrame properties, they are like implementation details
Leminkay
pushed a commit
to Leminkay/titanoboa
that referenced
this pull request
Oct 28, 2024
* fix VyperTraceSource.func_t this way is more robust * fix: handle errors in call tree, refactor TraceFrame move more data into TraceFrame properties, they are like implementation details * use net_gas_used for trace * fix call tree for create computations * fix call tree from internal functions * small refactor: BoaError.create() * factor out format_error
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.
What I did
print call trees on error
fix some bugs (related to modules, printing errors)
How I did it
How to verify it
Description for the changelog
Cute Animal Picture