Timeout parameter doesn't work when retry is configured

[geigerj]

Originally reported by @frankyn

What

Setting CallOptions timeout does nothing when the RPC is configured to retry.

To reproduce

video_service_client = Google::Cloud::VideoIntelligence::V1beta1::VideoIntelligenceServiceClient.new
features             = [Google::Cloud::Videointelligence::V1beta1::Feature::LABEL_DETECTION]                                                                                           
options = Google::Gax::CallOptions.new(timeout: 60)
path = "gs://cloudmleap/video/next/volleyball_court.mp4"
                                                                                                                  
operation = video_service_client.annotate_video(path, features, options: options) do |op|
  ...
end

Expected behavior

The call retries with an initial timeout of 60s.

Observed behavior

The call fails with "INVALID_ARGUMENT" due to an initial timeout of 19s; the configured timeout is ignored. It is possible to change the timeout only by manually configuring the full backoff settings.

[evaogbe]

I'm getting a different error:

GaxError Exception occurred in retry method that was not classified as transient, caused by
7:Google Cloud Video Intelligence API has not been used in project usable-auth-library before or it is
disabled. Enable it by visiting
https://console.developers.google.com/apis/api/videointelligence.googleapis.com/overview?project=usable-auth-library
then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our
systems and retry. (Google::Gax::RetryError)

[geigerj]

@eoogbe Try using the project gapic-test, which should have the API enabled already.

[evaogbe]

It's maxxed on keys. I can't create a new one.

[evaogbe]

Thank you for your bug report. Based on its current description, we are unable to reproduce it. If you are still experiencing this issue and are reasonably certain that it is a bug, please feel free to re-open this issue with additional information to help us reproduce it.

[geigerj]

@eoogbe we've updated the timeout configuration since the original bug report; are you sure you're not just seeing that? I'd be surprised if the root cause was fixed in GAX because AFAIK no work has been done there. Happy to sync offline in more detail.