Client config JSON files generated by gapic-generator sometimes include a timeout_millis field that sets the preferred default timeout for each call. (This value is used in the non-retry case. See Google::Gax.add_timeout_arg.)
As far as I can tell, this value is not being honored. Instead, the default timeout set in the gapic-generated client class is used. (This value seems to be hard-coded at 30s.)
This may be causing problems for services like Tasks, which currently implements a server-side limit of 30s on the timeout, and thus results in intermittent failures of this precondition.
This should probably be fixed in settings.rb in Google::Gax.construct_settings by reading any timeout_millis from the overriding_method hash.
Client config JSON files generated by gapic-generator sometimes include a
timeout_millisfield that sets the preferred default timeout for each call. (This value is used in the non-retry case. SeeGoogle::Gax.add_timeout_arg.)As far as I can tell, this value is not being honored. Instead, the default timeout set in the gapic-generated client class is used. (This value seems to be hard-coded at 30s.)
This may be causing problems for services like Tasks, which currently implements a server-side limit of 30s on the timeout, and thus results in intermittent failures of this precondition.
This should probably be fixed in
settings.rbinGoogle::Gax.construct_settingsby reading anytimeout_millisfrom theoverriding_methodhash.