SuccessfulKoala55 Nope. I didn't even get to enter my name. I suspect there is some mistake in mapping the data folder.
Was using the template in https://github.com/allegroai/clearml-helm-charts to deploy.

Hi TimelyPenguin76 , nope. I don't see any errors. That's why not sure what went wrong

JuicyFox94 and SuccessfulKoala55 Thanks alot. Indeed it is caused by dirty cookies.

It gets rerouted to http://app.clearml.home.ai/dashboard . with the same network error.

This is what I got. and when I see http400 error in the console.

Thanks. The examples uses upload_artifact which stores the files in output_uri. What if I do not want to save it but simply pass to next step, is there a way to do so?

Clearml 1.1.1. Yes, i have boto3 installed too.

Do u have an example of how I can define the packages to be installed for every steps of the pipeline?

I was browsing clearml agent gihub and saw this. Isn't this for spinning up clearml-agent in a docker and perform like a daemon?

By the way, will downloading still happen if the datasets is available in the cache folder? Any specific settings to add to Dataset.get_local_copy()?

Yea. Added an issue. We can follow up from there. Really hope that clearml serving can work, is a nice project.

Hi SuccessfulKoala55 Thanks for pointing me to this repo. Was using this repo.

I didn't manage to find in this repo that if we still require to label the node app=clearml, like what was mentioned in the deprecated repo. Although from the values.yaml, the node selector is empty. Would u be able to advise?

How is the clearml data handled now then? Thanks

Hello CostlyOstrich36 I am facing an issue now. basically i installed all necessary python packages in my docker image. But somehow, the clearml-agent does not seems to be able to detect these global packages. I don't see them in the "installed packages". Any advice?

I have yet to figure out how to do so, would appreciate if u could give some guidance

Thanks AgitatedDove14 . Specifically, I wanted to use my own clearml server and Triton. Thus, I attempted to use --engine-container-args during launch but error saying no such flag. Looked into --help but I guessed it is not updated yet.

Hi ExasperatedCrab78 I managed to get it. It was due to ip address set in examples.env.

Thanks

Hi @<1523701070390366208:profile|CostlyOstrich36> , basically

• I uploaded dataset using clearml Datasets. The output_uri is pointed to my s3, thus the dataset is stored in s3. My s3 is setup with http only.
• When I retrieve the dataset for training, using Dataset.get() , I encountered ssl cert error as the url to retrieve data was https://<s3url>/... instead of s3://<s3url>/... which is http. This is weird as the dataset url is without https.
• I am not too sure why and I susp...

Hi CostlyOstrich36 I have run this task locally at first. This attempt was successful.

When I use this task to run in a pipeline (task was run remotely), it cannot find the external package. This seems logical but I not sure how to resolve this.

Nope. In my local drive

OK I will send here shortly.

I figured out that it maybe possible to do these
experiment_task = Task.current_task()
OutputModel(experiment_task ).update_weights(' http://model.pt ') to attach it to the ClearML experiment task.

I not very sure tbh. Just want to see if this is useful....

I got SSL error few days back and I solved it by adding cert to /etc/ssl/certs and perform update-ca-certificates .

export REQUESTS_CA_BUNDLE=/etc/ssl/certs/ca-certificates.crt

Add this. Note that verify might not work with sdk.aws.s3.verify but sdk.aws.s3.credentials . Pls see the attached image.

Example:
aws {
s3 {
credentials: [
{
` ...

U want to share your clearml.conf here?

Nice. That should work. Thanks

Yup. But I happened to reinstall my server and the data is lost. And the agent continue running.

Yes. The training working well with cuda

May I know where to set the cert to in env variable?

seems like it was broken for numpy version 1.24.1.
Tried with numpy 1.23.5 and it works.

https://clear.ml/docs/latest/docs/integrations/storage/
Try add the <path to your cert> for s3.credentials.verify.