Jonathan Calvert
Jonathan Calvert
We've tested against 3.2 and 3.3.3 as well as master, also with the latest gRPC gem.
We can just run our fork so no big rush. We can dump the proxy specific bits you mentioned for this. It's a particularly odd and unexpected interaction.
We'll need to update this shortly because of a bug in the way it is structured. When code makes a bidi call, the write operation is run inside a [thread](https://github.com/grpc/grpc/blob/master/src/ruby/lib/grpc/generic/bidi_call.rb#L74)...
Updated again...looks like some of our forked stuff leaked over, so I cleaned that up.
@dv I'll try to clean this up here soon!
@dv I believe I have cleaned up the pull request. Thanks!
@jasonl AFAIK there's no further work to be done. I did the HoundCI cleanup and the tests pass; whatever Travis failures are there seem to be unrelated. We used a...