-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
chore(rpc): improve debug_traceBlock performance #11069
Conversation
First approach done, ready for review & feedback |
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.
this is slightly more complex, and requires a different approach, maybe like an Optional Inspector as argument and the trace_transaction also returns the inspector again
@@ -332,7 +341,7 @@ where | |||
Ok(frame.into()) | |||
}) | |||
.await?; | |||
return Ok(frame) | |||
return Ok(frame); |
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.
could you please undo these, makes it harder to review, idk why they keep reappearing...
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.
when you run cargo fmt
and not cargo +nightly fmt
...doom
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.
Oopsie, will update them
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.
About the approach does modifying the trace_transaction
function to accept an optional inspector and return it along with the result and then modify trace_block
function to use it sound good?
Implements #11066