What happened?
When a GrpcStreamBroadcaster successfully starts streaming, it should reset the reset strategy, otherwise, every time there is a problem, the retry counter is incremented, even if a connection was made, resulting in potential very long delays for the first retry after a successful connection broke).
What did you expect instead?
The retry strategy should be reset after a successful connection.
Extra information
There was a previous attempt to fix this (#148) but it failed because it used initial_metadata() to try to detect the connection success, but that doesn't work and had to be reverted (#204).
What happened?
When a
GrpcStreamBroadcastersuccessfully starts streaming, it should reset the reset strategy, otherwise, every time there is a problem, the retry counter is incremented, even if a connection was made, resulting in potential very long delays for the first retry after a successful connection broke).What did you expect instead?
The retry strategy should be reset after a successful connection.
Extra information
There was a previous attempt to fix this (#148) but it failed because it used
initial_metadata()to try to detect the connection success, but that doesn't work and had to be reverted (#204).