Termination of Multipleprocessing/Pool
Open
- Dominant language
- Python
- Stars
- 21
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
The multiple processing tasks do not seem to terminate themselves right away if the parental node is interrupted. If each process has an end then the process will be ended at the end eventually. But if a process falls in an infinite loop or becomes halted, the process will stay in the background even after the parental node is refreshed or the GPI is closed. Is it possible to have the mulitple processing framework to be controlled by the parental GPI node when interruption occurs?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.