Role based access controls are supported only in Scale/Enterprise versions.

I would suggest considering a Scale/Enterprise license. The amount of time you would be wasting in man hours on managing, doing hacks and patches on this and various other capabilities would most likely cost you in the long run much more than a license. Not to mention the dedicated support and other features you would be receiving.

For Enterprise related questions please use your dedicated Slack channel. You need to provide an extra index url, instructions are given in the ClearML Python Package Setup as shown in the screenshot:

It's cached for a bit of time in the backend

Is it the services docker that comes with the docker compose or did you run your own agent?

Unless you're running in docker mode, then I think the task will continue running inside the container. Might need to check it

That's an interesting idea 🙂
You should open a github issue for it!

Hi @<1529271085315395584:profile|AmusedCat74> , thanks for reporting this, I'll ask the ClearML team to look into this

Might need to refresh page after opening dev tools 🙂

WittyOwl57 , when creating credentials, the credentials are associated with your user. So even if you give others those credentials, the experiments in the system will show up under the user who's credentials were being used when running the experiment 🙂

Hope this helps

You can edit the mongodb manually (strongly suggest against) to change users of experiments. Besides that, I'm afraid not. Each user would have to create separate credentials for themselves under their own user in the system.

A suggestion I might have is using the 'Description' field to write down the relevant user manually and adding that as a column in your view. The small cogwheel near the top right (next to the refresh button) will give you the option to add that column.

Hope this helps...

Hi @<1523701079223570432:profile|ReassuredOwl55> , how are you saving them? Are they are saved as artifacts?

No need, that was intended for another chat 🙂

Also, can you add a screenshot please?

Hi @<1527096757119356928:profile|FrothyShrimp23> , what server are you using? Is it self hosted or the community, if self hosted, what version?

@<1527096757119356928:profile|FrothyShrimp23> , what browser / OS are you using ?

Thanks 🙂

Also, I'm not sure I understand exactly what you're expecting to get and what you're getting

Hi @<1696331935023894528:profile|BoredBee87> , role based access controls are available only in the Scale & Enterprise licenses. These licenses do support full on premise deployments. Besides role based access controls there are many other features available. I'd suggest contacting ClearML directly to hear about other options 🙂

top right corner

Hi BoredBat47 , this happens only when you use the --foreground flag?
Is this the full error? What version of clearml-agent are you using? What OS are you on?

Hi CrabbyKoala94 ,

Can you please open developer tools and see if you get some sort of error there?

Hi @<1724235687256920064:profile|LonelyFly9> , what data/information are you looking to get using the user id?

Hi @<1523703572984762368:profile|SlimyDove85> , conceptually I think it's possible. However, what would be the use case? In the end it would all be abstracted to a single pipeline

I'm not sure I understand this config, is this an autoscaler for GCP or AWS?

Where did you get this autoscaler? I don't think a GCP autoscaler was released in the open source

Try to set agent.enable_git_ask_pass: true for the agent running inside the container, perhaps that will help

Slow network or network died all of a sudden - you wouldn't want your experiments to fail just because there is a network issue. Once network is restored - everything is sent as it should be to the backend. This is the resilience I was talking about

Regarding mistake in URL - I guess it is your responsibility to keep track of not using wrong URLs. As I said before - How would you suggest the SDK know what is the 'right' URL and what is the 'wrong'...

This is also used in automated scenarios and over possible network issues, the retry is built in and is a good compromise - basically making the SDK resilient to network issues. The error you're getting is a failure to connect, unrelated to the credentials...

@<1523707653782507520:profile|MelancholyElk85> , Hi!

Do you have anything in the console regarding this? Also If you move to the 'INFO' tab in the experiment, there is a 'parent view' can you please validate that it links the parent to it?