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

Use LRU in connection-cache (backport #24109) #24322

Merged
merged 1 commit into from
Apr 14, 2022

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Apr 13, 2022

This is an automatic backport of pull request #24109 done by Mergify.
Cherry-pick of a38bd4a has failed:

On branch mergify/bp/v1.10/pr-24109
Your branch is up to date with 'origin/v1.10'.

You are currently cherry-picking commit a38bd4acc.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   Cargo.lock
	modified:   client/Cargo.toml
	modified:   client/src/connection_cache.rs
	modified:   programs/bpf/Cargo.lock

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   gossip/src/cluster_info_metrics.rs

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally


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

@mergify mergify bot added automerge Merge this Pull Request automatically once CI passes conflicts labels Apr 13, 2022
Switch to using LRU for connection-cache
@solana-grimes
Copy link
Collaborator

😱 New commits were pushed while the automerge label was present.

@solana-grimes solana-grimes removed the automerge Merge this Pull Request automatically once CI passes label Apr 13, 2022
@codecov
Copy link

codecov bot commented Apr 14, 2022

Codecov Report

❗ No coverage uploaded for pull request base (v1.10@9aa9587). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             v1.10   #24322   +/-   ##
========================================
  Coverage         ?    81.5%           
========================================
  Files            ?      584           
  Lines            ?   158945           
  Branches         ?        0           
========================================
  Hits             ?   129636           
  Misses           ?    29309           
  Partials         ?        0           

@ryleung-solana ryleung-solana merged commit 0e6ba29 into v1.10 Apr 14, 2022
@mergify mergify bot deleted the mergify/bp/v1.10/pr-24109 branch April 14, 2022 01:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants