Reputation
Badges 1
533 × Eureka!Okay, so let me get this straight
The autoscaling is basically an ever-running task (lets say on the services
queue). Now, the actual auto scaling and which queues exist have nothign to do with that, and are configured in the auto scale task?
I mean if I continue and build on the example in the docs, what will happen if the training
task is completed, and then I get it and log to it? Will it be defined as running again?
DangerousDragonfly8 but would this work if they are not concurrent but sequential?
Thx DangerousDragonfly8 💪
I was sure you are on Israel times as well, sorry for the night time thing 😄
When I ran the clearml-task --name ... -project ... -script ....
it failed saying not requiremetns was found
Wait but I don't want to execute it
when I specify --packages
I shoudl manually list them all not?
Nope, quite some time has passed since 🙂 I might be able to replicate it later... still battling with the pipeline to make it work
I couldn't do it with clearml task as it was looking for a requirements file and I'm workgin with poetry
` ClearML launch - launch any codebase on remote machine running clearml-agent
Creating new task
Error: requirements.txt not found [/home/elior/Dev/Projects/XXXXX/requirements.txt] Use --requirements or --packages `
I only want to save it as a template so I can later call it in a pipeline
Is tehre anything specific about the logs we're looking for? Because if I just dumop them it will take me a while to see no sensitive data and naming is there
First of all I wasn't aware that was an option - but I think it's preferable to be able to do it through the command line. Because I'm developing the pipeline to be executed remotely, but for debugging I run it locally.
Using what you showed I can obviously write it, and delete it once it is ready, and rewrite it when I'm debugging or adding features - but I think DX-wise it would be nicer to be able to trigger this functionality through the command line
I was trying out the pipeline controller for the first time and I felt a bit of a burden that just for the sake of trying I had to launch an agent
If this includes scheduling through pipelines, in my opinion there should be an option to execute a pipeline without an agent. Sometimes for development I just want to execute a pipeline on my local machine just as I would a task...
working directory is the same relative to the script, but the absolute path is different as the github action creates a new environment for it and deletes it after