Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Leader info refresher (backport #24597) #24810

Merged
merged 1 commit into from
Apr 30, 2022
Merged

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 28, 2022

This is an automatic backport of pull request #24597 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

In PR review https://github.com/solana-labs/solana/pull/24083/files#r852661162. We are concerned the leader info might be out dated if the retry queue is long causing large number transactions sent to outdated leaders and increasing the load in the network.

A leader info refresher is used to ensure the leader info is up-to-date before being used in sending transactions. The refresher can update the new leader with updated endpoints.

(cherry picked from commit 431c841)
@mergify mergify bot added the automerge Merge this Pull Request automatically once CI passes label Apr 28, 2022
@mergify
Copy link
Contributor Author

mergify bot commented Apr 28, 2022

automerge label removed due to a CI failure

@mergify mergify bot added automerge Merge this Pull Request automatically once CI passes and removed automerge Merge this Pull Request automatically once CI passes labels Apr 28, 2022
@mergify
Copy link
Contributor Author

mergify bot commented Apr 29, 2022

automerge label removed due to a CI failure

@mergify mergify bot added the automerge Merge this Pull Request automatically once CI passes label Apr 29, 2022
@mergify
Copy link
Contributor Author

mergify bot commented Apr 29, 2022

automerge label removed due to a CI failure

@mergify mergify bot added automerge Merge this Pull Request automatically once CI passes and removed automerge Merge this Pull Request automatically once CI passes labels Apr 29, 2022
@mergify
Copy link
Contributor Author

mergify bot commented Apr 29, 2022

automerge label removed due to a CI failure

@mergify mergify bot added automerge Merge this Pull Request automatically once CI passes and removed automerge Merge this Pull Request automatically once CI passes labels Apr 29, 2022
@codecov
Copy link

codecov bot commented Apr 30, 2022

Codecov Report

Merging #24810 (44bca9f) into v1.10 (b8040dc) will increase coverage by 0.0%.
The diff coverage is 90.4%.

@@           Coverage Diff            @@
##            v1.10   #24810    +/-   ##
========================================
  Coverage    81.5%    81.5%            
========================================
  Files         586      588     +2     
  Lines      159664   160487   +823     
========================================
+ Hits       130185   130878   +693     
- Misses      29479    29609   +130     

@mergify mergify bot merged commit 9bbb00b into v1.10 Apr 30, 2022
@mergify mergify bot deleted the mergify/bp/v1.10/pr-24597 branch April 30, 2022 04:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Merge this Pull Request automatically once CI passes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant