Repository navigation
v0.15.3
This release ensures upper-layer protocols are informed about closed connections and substreams that can no longer be opened.
Errors in TCP, QUIC and WebSocket connections now always close the connection and report it as closed. Previously, a peer could look connected forever and could not be connected to again.
When the primary connection to a peer closes and the secondary connection takes over, outbound substreams still opening over the closed connection are now reported as SubstreamOpenFailure, so requests sent over it fail with RejectReason::ConnectionClosed instead of hanging.