Support multicall3 in status endpoint
#151
Merged
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.
Before:
./cli status --podAddress 0x2641C2ded63a0C640629F5eDF1189e0f53C06561 3.60s user 4.62s system 5% cpu 2:38.98 totalAfter:
./cli status --podAddress 0x2641C2ded63a0C640629F5eDF1189e0f53C06561 1.71s user 1.00s system 25% cpu 10.646 total2:38m -> 10.6s
Tested by running on master/branch for a particular pod and asserting the JSON output. Used a graphical visualizer here so if any keys mismatched, I could figure out which ones. None did.
wooo