-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
objc[54401]: +[__NSCFConstantString initialize] may have been in progress in another thread when fork() was called. #1418
Comments
This helped me solve the same error when using functions_framework to test Google Cloud Functions locally. Many thanks |
Dear Daniel, thanks a stack, this saved my day when I was trying to invoke a worker function using Python's With kind regards, |
I have been searching every where for this you are God send. |
This doesn't seem to work under Monterey anymore. |
@Sshuichi: I'm using Monterey (12.3 21E230) and it still worked for me. 🎉 Unfortunately that probably means you've got a different issue to resolve. |
For anyone wondering why this works Reference |
A relevant blog post that also suggests the same fix: The author includes this warning:
|
thanks for that info, it saved my day... was blocked for that error |
Finally it got solved, that one export line took 1 day for me but now its fine |
Hm, I keep seeing everyone praising disabling fork safety rule... I'm wondering though, does anyone know if a more reliable fix is available in a newer version of python for example ? In my case - I am using 3.10 |
Putting this here so anyone else using rq with requests can find it.
On a brand new install of rq, e.g., create a new python3.9 virtualenv and pip install rq:
Then,
The solution is:
The text was updated successfully, but these errors were encountered: