[Issue] `context canceled` error when attempting to download Bicep during fresh `azd up`

[cecheta]

• Make sure you've installed the latest version using instructions

Output from azd version
Run azd version and copy and paste the output here:
azd version 1.23.0 (commit 9a02add)

Describe the bug
On a newly initialised install of azd, running azd up produces a context canceled error when attempting to install Bicep immediately after logging in. This happens consistently.

To Reproduce

1. rm -rf ~/.azd
2. Create new azd project, e.g. azd init --template todo-python-mongo
3. azd up
4. After logging in, the following error is seen:

ERROR: initializing infrastructure provider: failed resolving IaC provider 'bicep': downloading bicep: Get "https://downloads.bicep.azure.com/v0.39.26/bicep-linux-x64": context canceled

Expected behavior
After logging in, bicep is downloaded and the install begins.

Environment
Information on your environment:
Ubuntu 24.04.1 LTS (WSL2, Windows 11)

[rajeshkamal5050]

@cecheta could not reproduce it. Can you retry and attach logs with --debug?

demo % azd version
azd version 1.23.0 (commit 9a02add5930c2c87b6b2c78443e4d8132587417d)
demo % azd auth login
  Logged in to Azure as XXXXXX
demo % export AZD_DEMO_MODE=true
demo % azd init -t Azure-Samples/todo-python-mongo-aca

Initializing an app to run on Azure (azd init)

  (✓) Done: Initialized git repository
  (✓) Done: Downloading template code to: /Users/rajeshkamal/demo

? Enter a unique environment name: todo

SUCCESS: New project initialized!
You can view the template code in your directory: /Users/rajeshkamal/demo
Learn more about running 3rd party code on our DevHub: https://aka.ms/azd-third-party-code-notice
demo % azd up
  (✓) Done: Downloading Bicep
? Select an Azure Subscription to use: 32. Azure SDK Test Resources - TME
? Enter a value for the 'location' infrastructure parameter: 51. (US) East US 2 (eastus2)
Note: Running custom 'up' workflow from azure.yaml

Provisioning Azure resources (azd provision)
Provisioning Azure resources can take some time.

Subscription: Azure SDK Test Resources - TME
Location: East US 2

  |     ==| Comparing deployment state

[cecheta]

To reproduce the issue you shouldn't run azd auth login as its own step, instead log in when prompted via azd up.
Here are the debug logs

logs.txt

[rajeshkamal5050]

thanks for that insight @cecheta yes, I can repro it.

@wbreza anything related to the context cancel changes? #6446

demo % azd version
azd version 1.23.0 (commit 9a02add5930c2c87b6b2c78443e4d8132587417d)
demo % rm -rf ~/.azd
demo % azd init -t Azure-Samples/todo-python-mongo-aca

Initializing an app to run on Azure (azd init)

  (✓) Done: Initialized git repository
  (✓) Done: Downloading template code to: /Users/rajeshkamal/demo

? Enter a unique environment name: todo-demo

SUCCESS: New project initialized!
You can view the template code in your directory: /Users/rajeshkamal/demo
Learn more about running 3rd party code on our DevHub: https://aka.ms/azd-third-party-code-notice
demo % azd up
WARNING: You must be logged into Azure perform this action
? Would you like to log in now? Yes

  Logged in to Azure as foo@microsoft.com

  (x) Failed: Downloading Bicep

ERROR: initializing infrastructure provider: failed resolving IaC provider 'bicep': downloading bicep: Get "https://downloads.bicep.azure.com/v0.39.26/bicep-osx-x64": context canceled
demo %