Repository navigation
Conversation
Add a reusable connector for on-demand async client reconnection. Share connection attempts across callers and keep each session's requests and streams isolated. Never replay failed RPCs. Preserve the existing single-connection constructors and security hook API. Cover failure recovery, cancellation, and request deadlines. Related: kata-containers/kata-containers#14313 Signed-off-by: Tim Zhang <[email protected]>
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.
Add
Client::connect_withfor on-demand async reconnection using an application-provided connector, including transports that require a handshake.Related to kata-containers/kata-containers#14313 and follows up on #324. This addresses connection recovery only. Interrupted
WaitProcesshandling and recovery of lost exit results require a separate Kata fix.Tests cover write failures, concurrent recovery, cancellation, timeouts, and stream isolation. Both protobuf backends, existing examples, and a local Kata hvsock regression test pass.