On it

Sorry but its not clear

I'll check my phone

Hey Jake thanks for responding

that is because my own machine has 10.2 (not the docker, the machine the agent is on)

What does that mean? How can I access this data?

I really don't know, as you can see in my last screenshot, I've configured my base image to be 10.1

no need to do it again, I ahve all the settings in place, I'm sure it's not a settings thing

So just to correct myself and sum up, the credentials for AWS are only in the cloud_credentials_*

this?

Thx DangerousDragonfly8 💪

that's the only line starting with 192.168

👍

a third one?

thx martin

but I don't really know

yeah I know

I showed you this phenomenon in the UI photos in the other thread

Can you lend a few a words about how the not-pip freeze mechanism of detecting packages work?

When you are inside a project, the search bar searches for experiments

so if you want to search inside a specific project, go to that project and use the search bar, if you want to search all over, go to the project called "All Experiments" and search there

I dont think that has to do anything with the value zero, the lines that should come out of 'mean' and 'median' have the value of None under quantile, but have a dre_0.5 assoxiated with them. those lines appear in the notebook and not in the ui

Let's try

I mean the code in whatever form it is - I'm working with git specifically, but if i have diffs I'd like to see the code with the diffs applied

eventually i think it should display the contents of the script executed in the most straightforward manner regardless of version control

you can use pgrep -af "trains-agent"

😄

iwhat if

O_O

AgitatedDove14

Do i need to copy this aws scaler task to any project I want to have auto scaling on? what does it mean to enqueue hte aws scaler?

Thanks Martin, code runs as expected

AgitatedDove14
So I couldn't kill the service agent myself (permission denied, I'm not sudo). What I did is I docker-compose down ed, commented out only the environment variable of GOOGLE_APPLICATION_CREDENTIALS from the clearml services agent service and upped the docker-compose again. I enqueued the Cleanup Service and now it works. Really weird, looks like the setting of GOOGLE_APPLICATION_CREDENTIALS causes an error when set even though I'm 100% is it not used for storag...