Doug Fawley

The PR that implemented this ultimately needed to be rolled back (#3307); this should have been reopened at that time.

> `failed to receive server preface within timeout` This means the server (A, in this case) isn't sending an HTTP/2 settings frame at the start of the connection for some...

Thanks for the repro case. I have identified your bug: your `singleListener`'s `Addr()` method never returns, because `conn` is uninitialized when called before the first `Accept` call (which is what...

This work is blocked on https://github.com/golang/go/issues/22717.

What is the appropriate way to communicate the failure?

https://github.com/grpc/grpc-go/runs/5890293475?check_suite_focus=true (386)

https://github.com/grpc/grpc-go/runs/5558569509?check_suite_focus=true

> This would be consistent with other clients, that only suggest the expected format, but do not enforce it. Unfortunately, this feature was not well defined (e.g. there was no...

I brought this issue up with the other language leads. We didn't decide on anything concrete yet, but we will discuss it further later this week and come up with...

One more: 4. Maintain the same order provided by the name resolver. How important is this, given that the first RPC will go to the first ready subchannel, then eventually...