You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regarding the Tribler code, I see several instances of "something with a TaskManager" that manages "something with a TaskManager".
The procedure for managing these things is:
Create a child ("something with a TaskManager") in the parent ("something with a TaskManager") code.
Wait for shutdown.
Destroy the children.
Each child waits for shutdown (by the parent) itself. However, if there is a link with the parent, it needs to make sure that the parent has not shut down yet.
My proposal is to create a TaskManager.register_taskmanager() that simply shuts down the given task manager on shutdown. This avoids the above explicit management by downstream code bases.
The text was updated successfully, but these errors were encountered:
Regarding the Tribler code, I see several instances of "something with a TaskManager" that manages "something with a TaskManager".
The procedure for managing these things is:
Each child waits for shutdown (by the parent) itself. However, if there is a link with the parent, it needs to make sure that the parent has not shut down yet.
My proposal is to create a
TaskManager.register_taskmanager()
that simply shuts down the given task manager on shutdown. This avoids the above explicit management by downstream code bases.The text was updated successfully, but these errors were encountered: