Closed minghuaw closed 6 months ago
This could be a problem with my Azure account, which I need to investigate further.
This problem seems to be gone on my local machine after I signed in again on Azure CLI
The problem seems to be gone on the testing Azure VM instance as well. This seems to be a service disruption rather than problem with the SDK.
It was observed that creating new producer or consumer client using
azure_identity::DefaultCredential
would fail with the following error, but connecting using the connection string still works fine.The above error could result in an idling connection which could end up with another error
While this problem was observed when upgrading the dependency
azure_core
to"0.19"
, I have experienced the same error with version"0.18"
and the dotnet SDK on my local machine (mac) and an Azure VM. The dotnet SDK seems just hang forever and the message is never sent to the Event Hub.