Cherry-pick PRs to 1.3.x branch and release v1.3.0-beta.3 #1491
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
Description Improve reliability from the ethstats module The connectionWrapper was cherrypicked from go-ethereum upstream: ethereum/go-ethereum@82a9e11 (ethereum/go-ethereum#21404) Other changes Validator injecting its version to the proxy stats chunk Tested Manually in a local testnet Related issues Fixes #1395 Fixes #1397 Backwards compatibility Yes
…at's left in the block
The decrease to 2048 was due to inefficiencies in the tx pool which have now been fixed, so this sets it back to its original value.
oneeman
changed the title
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
Cherry pick a couple of PRs to the 1.3.x release branch:
Then update the version to v1.3.0-beta.3 which will be tagged as a release.
Other changes
Revert the change in default tx pool
GlobalPendingvalue. It was changed to 2048 in v1.3.0-beta.2 due to remaining inefficiencies with large tx pools. However, this is resolved by #1490, so this PR also sets it back to its original value of 4096.Tested