Change: Remove RemoteError
variant from StreamingError
#1325
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.
Changelog
Change: Remove
RemoteError
variant fromStreamingError
StreamingError
is intended to represent non-logic errors that occurwhile streaming data to a remote peer. A
RemoteError
does not belongin a stream RPC error and should instead be included as part of a
non-error response.
Upgrade tip:
No modifications are required for this change, as no related API
utilized the
RemoteError
variant.Change: Simplify
send_snapshot()
error type inChunked
The return error type of
openraft::network::snapshot_transport::Chunked::send_snapshot()
issimplified from
StreamingError<_, Fatal>
toStreamingError<_>
. Thischange is made because the remote
Fatal
error cannot be handled by thesending end and should not be produced at all.
Upgrade Tip:
If
Chunked
is used in aRaftNetworkV2
implementation to adapt the v1RaftNetwork
, simply remove the error handling forFatal
. Otherwise,no changes are required.
This change is![Reviewable](https://camo.githubusercontent.com/1541c4039185914e83657d3683ec25920c672c6c5c7ab4240ee7bff601adec0b/68747470733a2f2f72657669657761626c652e696f2f7265766965775f627574746f6e2e737667)