-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
repeatedly calling jwk.(Cache).Register() with WithWaitReady(false) may cause a deadlock #1250
Comments
Thanks, I'll look into it tomorrow. |
@shasderias Hmmm, I'm not sure if this is blocking or if it's just ... slow. In my testing I did observe things timing out, but after adding some print logs, the call to AddResource seem to all be returning eventually, in order. And if I give it enough workers, let's just say 50 (via I acknowledge there's something to be desired, but I have a feeling it's just bad performance. (which I'll work on, but just want to make sure if we're seeing the same symptoms) |
I'm a little short on time now, but my gut feeling is:
I've also managed to repro on I'll have a bit more time after the 19th, will try to validate the above/investigate further then if it's still necessary. |
This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. This does not mean your issue is rejected, but rather it is done to hide it from the view of the maintains for the time being. Feel free to reopen if you have new comments |
Describe the bug
Calling
jwk.(Cache).Register()
many times with thejwk.WithWaitReady(false)
option may result in a deadlock.Please attach the output of
go version
(also reproducible on 1.23.1)
To Reproduce / Expected behavior
Repro Repo
Run the following test.
Expected: the program to terminate.
Actual: the program deadlocks (see log below).
The issue is also reproducible with:
go test -v
run from the command line;The issue does not appear to reproduce with
go run
, although it may be the case that the problem is still present, just less likely to occur.The program does not always deadlock in the same iteration of the for loop.
The text was updated successfully, but these errors were encountered: