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
>>> import threading
>>> threading.enumerate()
[<_MainThread(MainThread, started 140077973014336)>]
>>> import parsl
>>> threading.enumerate()
[<_MainThread(MainThread, started 140077973014336)>, <Thread(Thread-1 (__atexit), started 140077889824448)>]
Expected behavior
Importing parsl should not be doing global environment stuff like starting threads: things like this should start ideally at in .start() methods, or less preferably in config object initializers, and be cleaned up by the relevant shutdown method.
I think, although I have not investigated, also starts a new thread in every place that runs parsl code - not only the submitting workflow where a user might explicitly says import parsl, but inside every individual htex worker.
Describe the bug
Since PR #3607,
import parsl
starts a thread.To Reproduce
Expected behavior
Importing
parsl
should not be doing global environment stuff like starting threads: things like this should start ideally at in.start()
methods, or less preferably in config object initializers, and be cleaned up by the relevant shutdown method.Environment
my laptop,
master
branch 6ac930ecc @yadudoc @khk-globus
The text was updated successfully, but these errors were encountered: