Improve Penumbra worker init reliability #233
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This PR prevents `getFreeWorker()` from setting `busy = true` whenever no workers are available and also fixes setWorkerLocation() when called post-init to correctly re-init worker threads.
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dmattia
approved these changes
Nov 4, 2022
eligrey
commented
Nov 6, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR prevents
getFreeWorker()from settingbusy = truewhenever no workers are available and also fixessetWorkerLocation()when called post-init to correctly re-init worker threads.Related Issues
Public Changelog
[none]
Security Implications
[none]