Kinda, yes, and this has changed with 1.8.1.
The thing is that afaik currently ClearML does not officially support a remotely executed task to spawn more tasks, so we also have a small hack that marks the remote "master process" as a local task prior to anything else.
UnevenDolphin73 did that fix the logging for you? doesn't seem to work on my machine. This is what I'm running:
` from clearml import Task
level = logging.DEBUG
logging_format = "[%(levelname)s] %(asctime)s - %(message)s"
t = Task.init()
Internally yes, but in
Task.init the default argument is a boolean, not an int.
We don't want to close the task, but we have a remote task that spawns more tasks. With this change, subsequent calls to
Task.init fail because it goes in the deferred init clause and fails on
Does ClearML somehow
any loggers from
module? We suddenly noticed that we have some handlers missing when running in ClearML
I believe it adds a logger, it should not remove any loggers,
What's the clearml version you are using ?
ClearML does not officially support a remotely executed task to spawn more tasks we do through pipelines, it that helps you somehow. Note that doing things the way you do them right now might break some other functionality.
Anyway, I will talk with the team and maybe change this behaviour because it should be easy 👍
UnevenDolphin73 looking at the code again, I think it is actually correct. it's a bit hackish, but we do use
deferred_init as an int internally. Why do you need to close the task exactly? Do you have a script that would highlight the behaviour change between