Closed hayd closed 2 years ago
Hello,
It's not a limitation of concurrent.futures
but rather the fact the parent process cannot infer where the child is stuck. Only thing it can do is realize the results did not come back in time and terminate the process.
If you want to understand where a process is blocked, you can printout/log the execution steps and see which one is the step which does not complete in time.
Closing this. Please re-open if you need more info.
Firstly, thank you for this library - it's great!
Suppose I have the following code:
This traceback doesn't show that the process was sleeping in b() when it timed out.
Is there a way to see that or is this a limitation on concurrent.futures ?