You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default core behavior is to end a stream with a non-OK status (usually UNAVAILABLE) as soon as the channel enters the TRANSIENT_FAILURE state, with an option wait_for_ready to keep waiting instead. The grpc-js library currently always behaves as though the wait_for_ready option is set. That should be changed to align the behavior with the C core.
The text was updated successfully, but these errors were encountered:
Hi @murgatroid99, curious if there has been any progress on this bug. This bug prevents fail-fast behavior in my client, which is necessary for my use case. I'm happy to contribute if the fix is accessible to someone new to gRPC internals.
The default core behavior is to end a stream with a non-OK status (usually UNAVAILABLE) as soon as the channel enters the TRANSIENT_FAILURE state, with an option
wait_for_ready
to keep waiting instead. The grpc-js library currently always behaves as though thewait_for_ready
option is set. That should be changed to align the behavior with the C core.The text was updated successfully, but these errors were encountered: