Doug Fawley

> The expected server-side stats event ordering is: This is the _current_ ordering. We should also discuss options like: - Removing "Begin", since the start of every RPC on either...

Note that the comments you've added in the above snippets only apply to the _server_. On the client, I believe we expect this ordering: `Begin->OutHeader->{InHeader (at most once)/OutPayload/InPayload (only after...

@MakMukhi is there any way to attempt to stimulate this race in a regression test? Why didn't our tests ever run into this problem?

I'm going to reopen this to track adding regression test cases as discussed offline: 1. ~~Use `WithWaitForHandshake()` in a case where the remote server never sends the preface, and ensure...

FYI: v1.9.1 has been released with the fix to this issue.

cc @ejona86 @markdroth

I'm not sure how that solves any problems. These packages are direct dependencies of grpc itself. So if we (gRPC) want to update them, we will also update our dependency...

Just to keep the discussion going: Perhaps you can separate your new `grpcencoding` package into another module that is only released at v0 and is opt-in for your users until...

Also, cc @bogdandrutu (the original PR author that added this dependency)

> we have no way to programatically tell which APIs are experimental right now from gRPC. Unfortunately, Go itself provides no way to programatically signal this, either: https://github.com/golang/go/issues/34409 We do...