This repository was archived by the owner on Jan 22, 2025. It is now read-only.
Fix quic client on TestValidator#27044
Closed
CriesofCarrots wants to merge 1 commit intosolana-labs:masterfrom
Closed
Fix quic client on TestValidator#27044CriesofCarrots wants to merge 1 commit intosolana-labs:masterfrom
CriesofCarrots wants to merge 1 commit intosolana-labs:masterfrom
Conversation
pgarg66
approved these changes
Aug 9, 2022
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Problem
TestValidator doesn't work with the quic client on by default (as in #26927, for example); namely, transaction send attempts time out. This is because the ContactInfo assignment for a TestValidator (in
Node::new_single_bind) uses different port logic than what the client expects (quic offsets are hard-coded in the client).Summary of Changes
Fix
Node::new_single_bind()to use the same port-assignment logic asNode::new_with_external_ipcc @willhickey -- feel free to rebase #26927 on this to hopefully get further.