Tx Recall and Call Only Test Fixes #120
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
praetoriansentry
requested review from
leovct and
gatsbyz
and removed request for
leovct
leovct
reviewed
Sep 15, 2023
leovct
approved these changes
Sep 15, 2023
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.
Description
Making some fixes to the behaviors of recall mode and the call only flag. There were some bugs which caused the same tx to be used over and over again.
Testing
polycli loadtest --rate-limit 1000 --requests 100 --concurrency 200 --recall-blocks 500 -v 701 --mode R --call-only --call-only-latest http://127.0.0.1:8545