-
Notifications
You must be signed in to change notification settings - Fork 173
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
Oso initialization is not thread safe #1665
Comments
I'm honestly expecting a "don't do that", but I figured i'd report the behavior upstream. |
(to be clear, this pattern of initializing objects wasn't my idea, it was already established in the application when i took over.) |
Thanks for bringing this to our attention! Confirming you're not blocked on this atm? Routing internally either way. |
Yeah, I fixed this in our case by doing some clever thread things so only one initialization can happen at once. |
Because Reasons:tm: (just don't ask), I was able to get some Weird errors from Oso that I believe stems from multiple parallel initializations.
The text was updated successfully, but these errors were encountered: