Skip to content
This repository has been archived by the owner on Jan 11, 2023. It is now read-only.

Configure long running operations timeout #2769

Closed
digaoddc opened this issue Apr 9, 2020 · 1 comment
Closed

Configure long running operations timeout #2769

digaoddc opened this issue Apr 9, 2020 · 1 comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Feature Request Mgmt This issue points to a problem in the management-plane of the library.

Comments

@digaoddc
Copy link

digaoddc commented Apr 9, 2020

Hello. I spent some hours debugging one test to figure out why a request that was recorded with VCR was taking 30 seconds to run. This is strange because the request was recorded so no real request was made.

I found this line was causing this behavior

.
Basically it waits 30 seconds to parse the response. This behavior is not good in test mode.

This option long_running_operation_retry_timeout could be passed in the client parameters or in the env vars.

Something like this:

options = {
  client_id: ENV['AZURE_CLIENT_ID'],
  long_running_operation_timeout: ENV['AZURE_LONG_OPERATION_TIMEOUT']
}

profile_client = Azure::Profiles::V2017_03_09::Mgmt::Client.new(options)

Can you help me with this?

@allenjzhang allenjzhang added Feature Request Mgmt This issue points to a problem in the management-plane of the library. and removed triage labels May 1, 2020
@azure-sdk azure-sdk added the customer-reported Issues that are reported by GitHub users external to the Azure organization. label Sep 24, 2020
@kurtzeborn
Copy link
Member

Thank you for your interest in Azure SDKs. As detailed in this retirement announcement, this repo is no longer supported as of December 31st 2021. Please find the up-to-date list of languages and services supported with Azure SDKs here: https://aka.ms/azsdk

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. Feature Request Mgmt This issue points to a problem in the management-plane of the library.
Projects
None yet
Development

No branches or pull requests

4 participants