This runs with line 8 commented out but raises the KilledWor

Question

This runs with line 8 commented out but raises the KilledWorker when it is run

Joe Schmid · Answer

< Nate Atkins> Maybe your Dask workers don t have the `requests` module installed Make sure to start them with a python environment virtualenv that has `requests` installed

Nate Atkins · Answer

I thought about that I checked to make sure I was starting the workers in the venv and directory that the working example runs in when I let the executor start the cluster It also seems like commenting out the requests get would still blow up as the model is still loaded Maybe this isn t the case as I don t fully understand what is getting passed from the scheduler to the worker I can check this by removing the package and see what happens

Nate Atkins · Answer

This is what I see in the dask worker output 2020 02 07 20 13 43 099 INFO prefect TaskRunner | Task retrieve url Starting task run objc 68582 + NSCFConstantString initialize may have been in progress in another thread when fork was called objc 68582 + NSCFConstantString initialize may have been in progress in another thread when fork was called We cannot safely call it or ignore it in the fork child process Crashing instead Set a breakpoint on objc initializeAfterForkError to debug distributed nanny INFO Worker process 68582 was killed by signal 6 distributed nanny WARNING Restarting worker

Nate Atkins · Answer

Got it <https github com darkskyapp forecast ruby issues 13> On MacOS Mojave export OBJC DISABLE INITIALIZE FORK SAFETY=YES

Joe Schmid · Answer

< Nate Atkins> Nice great find

Chris White · Answer

< Marvin> archive Unexpected error occured in FlowRunner KilledWorker

Marvin · Answer