Thank you, @<1523701070390366208:profile|CostlyOstrich36>

@<1523701070390366208:profile|CostlyOstrich36> any update here, by chance?

nvm, just saw it has to have a different signature for aws/non-aws addresses

Hi, @<1523701070390366208:profile|CostlyOstrich36>
No, I did not.

The address looks like this:
https://<my_file_server>/my_project/task_id/image.jpg

When I visit https://<my_file_server> I got OK in response. The image.jpg itself is also available to view locally at /opt/clearml/my_project/task_id/image.jpg and inside the file server container at /mnt/fileserver/ my_project/task_id/image.jpg

In my cleaml.conf I do not specify default_output_uri nor did I provide it when I initialize a task. Might it be that this is the reason? Because I've overwritten the config file a few times, and don't remember how it looked in the past.

Hi! Self hosted.

so it just calls upload_artifact

Hi @<1523701087100473344:profile|SuccessfulKoala55> , have you spot smth interesting here?
Thanks!

atm I use pre_execute_callback to validate the params but it'be great if I can restrict a user to specific options

@<1523701087100473344:profile|SuccessfulKoala55> could you assist, please?

And here's when I've tried to test the connection within the agent's container

@<1523701070390366208:profile|CostlyOstrich36> sure! Thanks for taking a look!)

like so:

Thank you @<1523701435869433856:profile|SmugDolphin23> !

probably you have to have ffmpeg libsm6 libxext6
packages installed in the docker container where you use opencv.

Hello @<1523701070390366208:profile|CostlyOstrich36>
Yes, I'm self hosting. Yes, there's an error (see the pic). It says ERR_BLOCKED_BY_ORB. But the address it sent request to is wrong. As I said it's double-encoded.

When i started agent with clearml-agent daemon --queue train it was 3.10.12. but I've installed the clearml itself and started the agent with bash were venv was not activated.

that issue was resolved by upgrading virtualenv to the latest version

no, if you open the task logs you can see that it's git@github.com :[domain]/[repo]

unless I'm missing something

Funny, because when I faced the issue I thought it would be easier to use ssh and not user/pass (because gitgub uses 2FA and I was not sure (still not) how ClearML works with it).

What if you'd try manually change REPOSITORY prop in cloned task from ssh style address to https style?

oh, I'm sorry, my bad. It's simply:

def log_file(self, file_name: str, file_path: str):
        self.task.upload_artifact(name=file_name, artifact_object=file_path)

Yes, looks like the solution, I've been working on it for the past 5min
Will let you know:)

Thanks a lot @<1523701070390366208:profile|CostlyOstrich36> ! Will take a look in a few hours.

2. the config as you show will try to use https connection in the first place, you have to remove user/pass for it to use ssh as far as I understand

And one more thing that relates to the q#1 - is it safe to use more resent base image for agent-services service in docker compose? I see the specified latest tag point to image which was updated like 3 years ago..

CLEARML-AGENT version 1.8.1

@<1523701087100473344:profile|SuccessfulKoala55> sure. Thanks for taking a look.

Hello @<1523701070390366208:profile|CostlyOstrich36>
Nothing you can help with here?
Thanks.

Hi @<1523701070390366208:profile|CostlyOstrich36> I'm talking about ClearML server itself

not the agents