add logging for the currently used rpc node #289
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
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 does this PR do?
Adds simple logging to see the currently used RPC NODE in the logging/stdouts
Related issue
Discord server/mev-inspect-py, plus I updated the .pre-commit-hook because mypy was failing, it needed a path to the executable for the env, naimly language_version: python3.9
If there isn't already an open issue, create an issue first. This will be our home for discussing the problem itself.
Testing
Tested on Ubuntu 20.04, Python3.9 (system version)
What testing was performed to verify this works? Unit tests are a big plus!
Checklist before merging
./mev test