Timeout configuration doesn't change Faraday's timeout

[jeremyjpark]

Hi there, I was trying to use the timeout configuration api parameter that was added in the 21.12 release and was not sure if I'm understanding its intended usage correctly. Our initializer is set up as follows:

AsposeWordsCloud.configure do |config|
  config.client_data['ClientSecret'] = ...
  config.client_data['ClientId'] = ...
  config.timeout = 120
end

It looks like the default adapter is Net Http for Faraday 1.10.0 which has a default timeout of 60 seconds.

I would like to extend the timeout for my requests to be greater than 60 seconds as specified in the configuration, but the api client makes it seem like the request will timeout at lesser of 60 seconds (from the default adapter) or the configured timeout (120 seconds in in my case).

Is there an existing way to specify the request timeout for Faraday when initializing the connection in the ruby sdk? Something with the same effect as

conn = Faraday.new url, { :params => query_params, ..., :request=> { :timeout => @config.timeout } do |f|
  ...
end

[nikhilgoyal22]

@jeremyjpark 💯 . I am facing the same issue and have mentioned the same thing in their forums multiple times.

@YaroslawEkimov can we get some info on this issue?

[tilalahmad]

@jeremyjpark , @nikhilgoyal22

We noticed that the timeout property was not working as expected in Aspose.Words Cloud SDK for Ruby and fixed it. The fix will be available in the July 2022 release of Aspose.Words Cloud SDK for Ruby.

[nikhilgoyal22]

@tilalahmad Nice 👍