-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[wasm] crypto deadlock fix #73537
[wasm] crypto deadlock fix #73537
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue Details
|
Co-authored-by: Ankit Jain <radical@gmail.com>
Co-authored-by: Ankit Jain <radical@gmail.com>
CI test with multiple workitems on Helix is #73629 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall this looks good to me. Thanks for fixing this!
I just had a few nit-ish comments.
re:having-spin-or-nonblocking-in-fn-name, I added those to make it obvious to spot cases where they might get used in incorrect contexts. For example, using a spin wait for a state inside a lock, which could cause a deadlock because the other side is waiting for that lock, so it can change the state. |
renamed the subtle-crypto.ts file, because that's not a worker
/azp run runtime-wasm |
Azure Pipelines successfully started running 1 pipeline(s). |
Fixes crypto deadlock: Log on main