-
Notifications
You must be signed in to change notification settings - Fork 345
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
add withLog parameter to debug_traceCall #2897
Conversation
Coverage Report@@ Coverage Diff @@
## master aleks-debug-trace-call-options +/- ##
==================================================================
+ Coverage 80.90% 80.92% +0.02%
Files 286 286
+ Lines 81838 81932 +94
==================================================================
+ Hits 66206 66303 +97
- Misses 15632 15629 -3
|
…d with_log parameter from TraceType::Raw
…routed it to call_list listener
Co-authored-by: Aleksandar Brayanov <[email protected]>
WASM runtime size check:Compared to target branchMoonbase runtime: 2184 KB (no changes) ✅ Moonbeam runtime: 2120 KB (no changes) ✅ Moonriver runtime: 2132 KB (no changes) ✅ Compared to latest release (runtime-3102)Moonbase runtime: 2184 KB (+244 KB compared to latest release) Moonbeam runtime: 2120 KB (+220 KB compared to latest release) Moonriver runtime: 2132 KB (+232 KB compared to latest release) |
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.
I left a comment on the test, other than that it looks good to me !
What does it do?
Adding additional parameter to
debug_traceCall
that enables returns of logs calls similar to Geth's tracerWhat important points reviewers should know?
Is there something left for follow-up PRs?
What alternative implementations were considered?
Are there relevant PRs or issues in other repositories (Substrate, Polkadot, Frontier, Cumulus)?
What value does it bring to the blockchain users?