-
Notifications
You must be signed in to change notification settings - Fork 865
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KeyVaultChallengePolicy violates guarantees because it is not goroutine-safe #24031
Comments
I updated the SDK to the latest version and the issue persists. go.mod snippet:
|
Also happens on SDK Git commit |
Hi @strager! Thank you for your detailed report and PR! We'll look into this issue and decide if it makes sense to add to the SDK. |
The versions of |
Hi @strager. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue. |
@jhendrixMSFT I just tested with I don't see a version v1.1.1 for github.com/Azure/azure-sdk-for-go/sdk/security/keyvault/internal:
|
Ooops my fault, |
Bug Report
import path:
github.com/Azure/azure-sdk-for-go/sdk/keyvault/azsecrets
SDK version: unsure. Here is what go.mod says:
output of
go version
:go version go1.23.2 darwin/arm64
What happened?
When I use an azsecret.Client from multiple goroutines, Go's race detector complains. For example:
I expect to be able to use a Client from multiple goroutines. This is my understanding of the documentation here: https://learn.microsoft.com/en-us/azure/developer/go/azure-sdk-core-concepts Specifically: "Goroutine safety allows multiple goroutines to access a single client object concurrently."
I can work on a reduce repro if you need it.
The text was updated successfully, but these errors were encountered: