python: configuration field for LRO polling interval is not correct
See original GitHub issueThe generated code for client assumes long_running_operation_retry_timeout
, but its operation assumes long_running_operation_timeout
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Doc of how to adjust op status polling interval #1120 - GitHub
Is there a document and example showing how to control the interval at which Azure Python SDK polls operations for completion?
Read more >Set Polling Interval on Python Openzwave - Stack Overflow
1 Answer 1 ... [if] set to true (via SetPollInterval), the pollInterval will be interspersed between each poll (so a much smaller m_pollInterval...
Read more >Polling interval multiplier - GitLab Docs
Configure. To adjust the polling interval multiplier: On the top bar, select Main menu > Admin. On the left sidebar, select Settings ......
Read more >python-can.pdf - Read the Docs
python -can runs any where Python runs; from high powered computers with commercial CAN to USB devices right down to low powered devices...
Read more >REST API Modular Input - Polling Interval is not working
Hello Everyone, I try to use the REST Api Input in my splunk account but i have an issue. The "Polling Interval" value...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @yugangw-msft, thanks for spotting this!
After discussing possible fixes with @lmazuel, we’re thinking that we will remove this (and other options) from the constructor of the client, so these will need to be set specifically on client.config like you are currently doing in your workaround.
This should help us reduce the size of the generated code.
For example, the generated code will become:
And this would be consumed and configured like so:
This is a breaking change - so will be rolled out into the next major version of the Azure SDK for Python.
What do you think?
Cheers, Anna
@fearthecowboy indeed already fixed