Provide more specific errors messages for failing channels #984
Conversation
This file contains 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
Motivation: If a connection attempt fails, the reason for the failure should be propagated to the RPCs. Modifications: - Store errors in the active and ready states so that they can be used as contextual information when requesting a channel from the transient failure or shutdown states Result: - Connection level errors get propagated to RPCs made on that same Channel
Lukasa
approved these changes
Oct 5, 2020
|
Hmmm the Travis CI run passed, not sure why it isn't listed here though. |
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.
Motivation:
If a connection attempt fails, the reason for the failure should be
propagated to the RPCs.
Modifications:
as contextual information when requesting a channel from the transient
failure or shutdown states
Result:
Channel