Odd Error When Collecting Results from ProcessPool about pebble HOT 9 CLOSED

Hello,

thanks for reporting this.

The issue happens when the Pool is shutdown and does not compromise its functionalities. You see the stack trace because the library logs internal problems. Nevertheless, the crash itself happens in a separate thread and should not affect your application.

I will try to spin a Windows 10 environment and test it as soon as I have some time.

from pebble.

Thanks. I've been playing with the concurrent decorator as well on the same win10 system and haven't seen any issues there.

from pebble.

A more in depth explanation of what might be happening is here: https://bugs.python.org/issue19565

Haven't tried to reproduce it yet.

from pebble.

I managed to get a Windows machine to try out the issue. It seems the error is correctly handled by pebble but yet the crash is shown on the stderr.

My suspect is this line. The print_exc prints the traceback on stderr which would explain why the error seems coming from the Python internals rather than pebble modules. pebble correctly handles the excepition which is expected to happen when the Pool is shutdown.

I am not sure why the Python community decided to force print the traceback of an exception even when it is expected and handled. I guess the only workaround would be to rework the pool shutdown logic to make it more clean with Windows. This might take a while as it's a quite delicate procedure.

tl;dr: the output you see is not causing any real issue or compromising your application stability. It's just an annoying spurious log.

from pebble.

Version 4.3.10 should address this issue. Could you please verify and confirm? Thanks.

from pebble.

This should be fixed in 4.3.10 as for #35. Closing the issue. Please feel free to re-open if you are still affected by it.

from pebble.

FYI, I had to revert the fix as it was causing deadlock issues. I will try to find another way to silence the noise.

from pebble.

+1 on this. Having the same issue.

from pebble.

Fix added in release 4.6.0.

Closing this issue, please re-open it if the problem persists.

from pebble.