fix: proper usage of debug_traceTransaction [APE-1195]
#57
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
vany365
changed the title
debug_traceTransactiondebug_traceTransaction [APE-1195]
tests fail in ci because it is from a fork, but all is well
|
fubuloubu
previously approved these changes
Sep 1, 2023
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
The normal structlog tracer is actually not supported in Alchemy, not sure how that gone unnoticed.
But they do support the call tracer tracer, but that just makes call tree nodes really...
How I did it
callTracerapproach as a backup when Parity style fails (not sure if that actually ever happens tho)How to verify it
Checklist