Vadym Matsishevskyi

+1 Unless the current implementation is fundamentally wrong, I think just making the documentation match the implementation is better. Documenting is easier. Also, sometimes "fresh eye" view could be an...

@dpcollins-google Is current gax causing errors or warnings for you? If it is just warnings, given that those classes are used literally everywhere in whole google cloud and Ads libraries...

@bdhess, @sduskis, @songy23 I'm really confused by this issue and do not understand what we are trying to achieve here. Yes, there are differences between Go and Java clients, there...

Hi @nwbirnie, This looks doable, since `TransportChannelProvider` is `@InternalExtensionOnly` and `GrpcInterceptorProvider` and `LocalChannelProvider` are `@BetaApi` (so we can add extensions without formally breaking backward compatibility). At the same time, this...

@elharo @lesv Can you please provide more context here? I.e. why should we do it?

Was the previous fix done by increasing timeout somethign from 10 ms to 50 ms? That could be just not enough difference. In many of our tests we use timeout...

@chanseokoh There are no other clients besides java-compute depending on rest transport right now. So it is safe to ssume that all reported issues, if they are not compute related...

There are currently two APIs affected by this issue: ``` //google/cloud/dataform/v1alpha2/dataform_py_gapic_test //google/cloud/networkservices/v1/networkservices_py_gapic_test ```

This is the site packages issue which has caused many different issues for us. Some details about it: https://github.com/googleapis/gapic-generator/issues/3334#issuecomment-768156415.

@vchudnov-g Did you have a chance to do the check? This issue is out of SLO now.