multiprocessing.joinablequeue error when running demo code in jupyter lab about mantichora

[TaiSakuma]

Thank you for letting me know. I'll have a look.

[drhades]

For reference,
defining task_loop() in another python file and importing, it'll be ok.

[TaiSakuma]

Yes, I'm just working on this now. The code in this branch might work.

[TaiSakuma]

I released the version 0.9.8.

It works fine in Python 3.8 on Jupyter Notebook in my environment.

Please let me know if the problem persists.

The cause of the problem appears to be the change in the default start method in multiprocessing in Python 3.8. The default start method was "fork" until Python 3.7. But it changed to "spawn" in Python 3.8. The spawn method has more restrictions on how the main module is written as described in this section of the document for mulriprocessing. The mantichora version 0.9.8 uses the "fork" mode.

[drhades]

@TaiSakuma
Thanks for your quick fix and detail explaination!

After upgrading to 0.9.8, the above demo code work well,
but I get the following error:

when using mantichora background, code like:

def task_func(*args)
    for i in atpbar(...):
        do some network things
    return something

def parallel_func()
    split something into K parts
    task_partial = partial(task_func, ...)
    with mantichora() as mcore:
        for i in range(K):
            mcore.run(task_partial, ...)
        mcore.receive_all()

It works fine by 0.9.7.

[TaiSakuma]

Thank you for letting me know. I will look into it.

[TaiSakuma]

I released mantichora version 0.9.9.

I added the option mp_start_method to mantichora() so that uses can choose the start method of multiprocessing. The possible values are fork, spawn, and forkserver. The default is fork. For example, if you would like to use the spawn method, which was used in mantichora v0.9.7 in Python 3.8, you can do so as

mantichora(mp_start_method='spawn')

The spawn and forkserver mothods have more restrictions, which are already mentioned above in this issue.

If you need to use the fork method, you might get the same error of may have been in progress in another thread when fork() was called. If you are getting the same error and you are on MacOS, setting the environment variable OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES might solve the problem as suggested at StackOverflow here, which you might have found already.

Please let me know if this doesn't solve the problem or causes other problems.

Thank you.

[TaiSakuma]

I assume that the issue has been resolved. Please create a new issue if not.