should deadlines apply to streaming rpcs?

[callmehiphop]

I'm not sure if this is intended or not (it very well might be) but when a deadline is set for a streaming rpc the stream shuts down with a Deadline Exceeded error regardless of whether or not a connection is made once the deadline is hit.

I think this might be leading to strange behavior where the deadline must be increased by a great margin in order to allow the stream to stay open for longer. However this can be a problem in the event of an actual timeout, potentially causing client code to hang longer than necessary.

I think this is a gax issue because it applies default deadlines for streaming rpcs with no way to opt out, however this might also be a grpc issue? I'm not really sure, but I figured I'd start here!

[vchudnov-g]

@alexander-fenster Any updates?

[alexander-fenster]

@callmehiphop This was lost in the list of issues for a long time :)

For proper triaging: do you have any ongoing problems with the deadlines being applied to streaming methods in any of the libraries you support?

[callmehiphop]

@alexander-fenster currently no, however we could definitely simplify code in the PubSub client if this were behaving as expected.