feat: clean up tracing in robust provider #258
Merged
Conversation
This file contains hidden or 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
0xNeshi
reviewed
Dec 15, 2025
Collaborator
0xNeshi
left a comment
0xNeshi
left a comment
There was a problem hiding this comment.
Good thinking splitting the logging work into per-crate PRs 👍
LeoPatOZ
force-pushed
the
improve-logging-robust
branch
from
3b82bb8 to
8e7865d
Compare
0xNeshi
reviewed
Dec 17, 2025
0xNeshi
reviewed
Dec 17, 2025
0xNeshi
reviewed
Dec 19, 2025
0xNeshi
previously approved these changes
Dec 22, 2025
0xNeshi
approved these changes
Dec 22, 2025
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.
Towards #52
For now deals with robust provider logging.
Removes majority of
info!adds debug tracing to rpc methods (similar to how alloy does it).