grpc-js: Propagate error messages through LB policy tree #2868
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.
This modifies the
ChannelControlHelper#updateState
function signature to add anerrorMessage
argument, which can be either a string or null. The expectation is that it should be a string when the status is TRANSIENT_FAILURE, and null otherwise. The purpose of this is to enable LB policies with multiple children to provide some error information from clients when synthesizing an aggregate status to be passed to their parents. In order to avoid including excessive information in the status message, each such LB policy only passes along the last error message it has seen from any child.