fix(rust): auto-reconnect on transport errors after server restart#2880
Open
fix(rust): auto-reconnect on transport errors after server restart#2880
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2880 +/- ##
============================================
+ Coverage 68.33% 68.50% +0.16%
Complexity 739 739
============================================
Files 1053 1053
Lines 84763 84763
Branches 61297 61307 +10
============================================
+ Hits 57923 58065 +142
+ Misses 24468 24312 -156
- Partials 2372 2386 +14
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
861a948 to
f0201e8
Compare
mmodzelewski
approved these changes
Mar 5, 2026
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.
The SDK's send_raw_with_response() only triggered reconnect for a
subset of errors (Disconnected, EmptyResponse, Unauthenticated,
StaleClient). Transport-specific write errors like TcpError,
ConnectionClosed, WebSocketSendError, and QuicError were not in
the list, causing producers and consumers to loop forever on a
dead connection instead of reconnecting.
Added all transport-specific errors to the reconnect match in
TCP, WebSocket, and QUIC clients. TLS connections use the same
error types and code path, so they are also covered.
Integration tests verify both producer and consumer reconnect
across all three stateful transports (TCP, WebSocket, QUIC).