
Reputation
Badges 1
86 × Eureka!Configuration completed now; I t was a proxy issue from my end
However running my pipeline from a different m achine still gives me a problem
We're initialising a task to ensure it appears on the experiments page;
Also not doing so gave us issues of ‘Missing parent pipeline task’ for a set of experiments we had done earlier
I'm asking this because my kwargs is observed as an empty dict if printed
Alright then, the server worked as it should so far, thanks 😄
Here's the code, we're trying to make a pipeline using PyTorch so the first step has the dataset that ’ s created using ‘stuff’ - a local folder that serves as a package for my code. The issue seems to be in the unpicking stage in the train function.
I had initially just pasted the new credentials in place of the existing ones in my conf file;
Running clearml-init now fails at verifying credentials
Umm I suppose that won't work - this package consists of .py scripts that I use for a set of configs and Utils for my model.
Yes, I can pull other containers from dockerhub
I'm facing the issue during the initial set up of clearml serving - i.e the step where you use docker-compose to launch the serving containers
David,
I haven't provided a monitor_model parameter
But it seems to upload the model on noticing torch.save irrespective
More context:
I have agents running the stages and the pipeline being executed locally here.
A simple StorageManager.download_folder(‘url’)
My minio instance is hosted locally, so I'm providing an url like ‘ http://localhost:9000/bucket-name%E2%80%99
http://localhost:9000 http://localhost:9000/%3Cbucket%3E
My minio instance is hosted locally at the 9000 port.
2022-07-12 13:41:39,309 - clearml.Task - ERROR - Action failed <400/12: tasks.create/v1.0 (Validation error (error for field 'name'. field is required!))> (name=custom pipeline logic, system_tags=['development'], type=controller, comment=Auto-generated at 2022-07-12 08:11:38 UTC by mbz1kor@BMH1125053, project=2ecfc7efcda448a6b6e7de61c8553ba1, input={'view': {}})
Traceback (most recent call last):
File "main.py", line 189, in <module>
executing_pipeline(
File "/home/mbz1kor...
Yep, no clue why I had two of them either;
It started my pipeline and a few seconds in, another pipeline shows up