{Core} Increase threadpool timeout to 60 seconds. #32836
{Core} Increase threadpool timeout to 60 seconds. #32836DanielMicrosoft merged 1 commit intoAzure:devfrom
Conversation
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR. Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
There was a problem hiding this comment.
Pull request overview
This PR increases the module load timeout from 30 seconds to 60 seconds in the Azure CLI core. The timeout is used as a safety valve during parallel module loading to prevent indefinite hangs when loading command modules.
Changes:
- Doubled the MODULE_LOAD_TIMEOUT_SECONDS constant from 30 to 60 seconds
Comments suppressed due to low confidence (1)
src/azure-cli-core/azure/cli/core/init.py:40
- The comment "Timeout (in seconds) for loading a single module" is misleading. This timeout is used with
concurrent.futures.as_completed()on line 634, which means it's the timeout for waiting for the next completed future in the iteration, not a timeout for a single module's execution. Consider updating the comment to more accurately reflect this behavior, such as "Timeout (in seconds) for waiting for next module to complete during parallel loading. Acts as a safety valve to prevent indefinite hangs"
# Timeout (in seconds) for loading a single module. Acts as a safety valve to prevent indefinite hangs
MODULE_LOAD_TIMEOUT_SECONDS = 60
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Related command
Description
Noticed occasional timeouts on WSL with
mntdrive, for the larger modules (vmfor example), increasing the timeout for threads as a safety measure.Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.