thanks so much Jake!! appreciate it

Clarification question: was cache_executed_step present in clearml 0.17 (which we are running)? I am trying to add it in manually and it is giving me an unexpected keyword argument error

Hi Martin, this is indeed the case. I am not passing cache_executed_step=false to the controller but I assume this is the case as it is false by default

"extra_clearml_conf" : """ aws { s3 {key: "A" secret : "B" region: "C" }} """,

when copying my clearml config into the "Edit configuration menu" and running it, I am getting a Json decode error (expected "," before the aws)

I'm hoping to connect to the bucket inside of the VPC

For usage examples, it's difficult as the caching seems to be sporadic (works 90% of the time)

Thanks for the quick reply! I tried your suggestion and its telling me that the aws line is an invalid control character now

I just sent you a dm with the scrubbed autoscaler config, would you be able to give some pointers on overarching things that are wrong?

Thanks! 🙂

Hi Jake, we aren't using any specific use-case or example but this has been occurring sporadically throughout the last month or so. Would it be possible to hop on a 15 or so minute zoom call some time to show you what has been happening?

https://docs.aws.amazon.com/vpc/latest/privatelink/vpce-interface.html

any idea how to fix this? https://allegro.ai/clearml/docs/docs/examples/services/aws_autoscaler/aws_autoscaler.html seems to indicate we can just directly past the info into the block string

AgitatedDove14

The overall format seems to be slightly different between my local clearml conf and the accepted strings