When the subscription is stopped by cancelling the token, the gRPC call gets properly aborted, and it produces an exception, which is incorrectly treated by the client as an error. It leads to pollution of false errors in the logs:
As this cancellation behaviour is expected, it should not produce any error-level log messages.
When the subscription is stopped by cancelling the token, the gRPC call gets properly aborted, and it produces an exception, which is incorrectly treated by the client as an error. It leads to pollution of false errors in the logs:
As this cancellation behaviour is expected, it should not produce any error-level log messages.