Repository navigation
Conversation
We used to only apply the peer's `max_udp_payload_size` to the currently-active path upon reception of the peer's transport parameters. The value was not persisted in `RecoveryConfig`, which meant new paths discovered after the transport parameters were processed ignored this value. Fix this by updating `RecoveryConfig` with the value we receive, similar to `max_ack_delay`.
TheJokr
force-pushed
the
send-payload-conn-migration
branch
from
October 26, 2026 12:08
d103b07 to
771b843
Compare
This branch has not been deployed
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 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.
We used to only apply the peer's
max_udp_payload_sizeto thecurrently-active path upon reception of the peer's transport parameters.
The value was not persisted in
RecoveryConfig, which meant new pathsdiscovered after the transport parameters were processed ignored this
value.
Fix this by updating
RecoveryConfigwith the value we receive, similarto
max_ack_delay.