Doug Fawley

@annismckenzie no worries, I am just trying to understand your concerns with the design, if you have any. I'm hopeful a few folks here will at least briefly look it...

It finishes for me, you just have to be patient: ``` $ go run benchmark/benchmain/main.go -benchtime=10s -workloads=streaming -compression=off -maxConcurrentCalls=200 -trace=off -reqSizeBytes=1048576 -respSizeBytes=1048576 -networkMode=LAN -cpuProfile=speedup.cpu Stream-traceMode_false-latency_2ms-kbps_102400-MTU_1500-maxConcurrentCalls_200-reqSize_1048576B-respSize_1048576B-Compressor_false: 50_Latency: 40.3235 s 90_Latency: 41.0967...

> It'd be trivial to avoid the false positive by not emitting the diagnostic for channel receives. But doing so would cause us to miss many actual bugs. Is it...

Only one. As a matter of principal, I don't add annotations in my code in order to make tooling happy. Tooling should work correctly with the code as written, not...

> @dfawley does grpc support such feature? No, gRPC does not support any kind of stream multiplexing. I think the subsequent discussions in this thread are all accurate. It's perfectly...

+1 - especially with Hacktoberfest going on right now, we've had several people try to claim issues, but then disappear. Being able to automatically unassign them after a week or...

`Dispatched` is used to allow another protocol to handle the connection. That's not intended for this kind of use case. Interesting sequence of events. It seems if we use TLS...

Yes, this is on our radar, we will try to get it done this week or next.

I was hoping we could get it done this week, but it looks like that isn't going to happen. So, hopefully early next week. There is nothing blocking us at...

Reference from gRFC: https://github.com/grpc/proposal/blob/master/A6-client-retries.md#limits-on-retries-and-hedges We never implemented this particular "channel arg" in Go.