Doug Fawley

> Is there an issue open for this? I feel that it would make sense to open an issue, discuss the options we have, finalize one, and then move on...

Options: 1. Forbid the use of `t.Run` and require a `grpctest.Run()` that does what we need instead. 2. Replace `*testing.T` in the function signature with `*grpctest.T` and embed a `*testing.T`...

I think I like (2) the most of these options. I don't think it would be hard to implement, and changing all the existing tests isn't too hard with a...

Proposal: 1. Add new settings: ```go package grpc func WithStaticStreamWindowSize(int32) DialOption func WithStaticConnWindowSize(int32) DialOption func StaticStreamWindowSize(int32) ServerOption func StaticConnWindowSize(int32) ServerOption ``` These will behave the same as the current options....

Are you still able to reproduce this? Can you run with full debug logging enabled and include the logs? https://github.com/grpc/grpc-go#how-to-turn-on-logging

> @dfawley Will check and update; Though any idea on what is happening in this scenario? No idea. If your machine can't resolve `localhost`, or properly connect to an address...

Apologies for the breakage! This field needed to be removed for performance reasons as we no longer create a full contiguous copy of the serialized data (except within the default...

I spoke with the leads from Java & C++. They don't have any easy way to do exactly what you want, either. I'd probably recommend using the generic interface, which...

@mohdjishin do you have a proposal for how we could change things to do that?

> we most likely will stabalise it in next 1-2 releases unless decided otherwise. The option itself is what's experimental, really. It will become the default on the next release:...