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 tpu client next in validator with receiver 2 #3893

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

KirillLykov
Copy link

@KirillLykov KirillLykov commented Dec 3, 2024

Problem

  • add flag to validator to use tpu-client-next,
  • add tests on rpc side to work with both ConnectionCache and tpu-client-next
  • all the plumbing to select client on the validator side

Summary of Changes

Copy link

mergify bot commented Dec 3, 2024

If this PR represents a change to the public RPC API:

  1. Make sure it includes a complementary update to rpc-client/ (example)
  2. Open a follow-up PR to update the JavaScript client @solana/web3.js (example)

Thank you for keeping the RPC clients in sync with the server API @KirillLykov.

};

static GLOBAL_RUNTIME: LazyLock<TokioRuntime> = LazyLock::new(|| {
Copy link
Author

@KirillLykov KirillLykov Dec 3, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably, it would be better to define it validator/src/main.rs and pass to the Validator::new. But doing so would require changing new which means a lot of changes in the codebase. I propose to do so in separate PR which is not necessary to backport

@KirillLykov KirillLykov force-pushed the klykov/use-tpu-client-next-in-validator-with-receiver-2 branch from 9a2de64 to 4670c01 Compare December 3, 2024 17:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant