Volodymyr Magamedov

> Is it expected that people will want to re-use channels? In that case this will cause errors if someone tries to re-use it. In that case we should use...

Hello, I totally agree that this can be fixed before 0.5 release and without breaking backward compatibility. I'm only asking to avoid creation of extra "properties" for simplicity. I suggest...

It would be great to have this option. Looking forward to review and merge your PR.

Released `grpclib==0.4.3rc3` with updated `*_pb2.py` files

@upcFrost gRPC states that `protobuf` is not the only way to serialise requests and replies, so in `grpclib` it is optional 🤷🏻‍♂️ Health checks are also optional as some other...

I think that Google's `protobuf` and `grpcio` projects have some problems with versioning. Two times they broke backward compatibility in `protobuf`. Right now `grpcio-tools` requires `protobuf=3.12.0`, so even if `grpcio-tools`...

Can you search in your logs the reason why connection was closed? Possible reasons: - received `GOAWAY` frame from the server - lost TCP connection - connection was closed on...

@Gobot1234 Fixed your case in https://github.com/vmagamedov/grpclib/commit/d02ef84e6057cf889ed19f396da9325d77ad67b5. As you can see it was caused by `ChannelFor` testing utility - calling `Protocol.data_received` after connection was closed.

For sure client-side load balancing is an important feature. In order to quickly discover new instances and drain old ones it is better to use special protocol for look-aside load...

This error happened because data was received after connection (not underlying connection but connection's state in grpclib) was closed (there are many reasons). This kind of error should be a...