all: live chain-aware tracing - add tracers subscription #27694
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 comment was marked as spam.
This comment was marked as spam.
|
This is pretty heavily bitrotted (as can be expected since it was based on a fast-moving target). However, #29189 was just merged, so if you want to revisit this, now would be a good time to rebase it on master. |
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.
Depends on #27629.
This PR makes it possible to subscribe to traces being produced during normal block processing. So you can do
eth_subscribe('traces')and get notifications from the tracer that has been configured on node start-up to be run alongside the chain. Details of the notifications depend on each tracer. This PR only as a sample adds some notifications in the Printer.Todo： find a solution that works for all tracers.