Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hi, I Am Trying To Setup An Auto Scaler, But I Am Getting The Following Dependency Error:

Hi,

I am trying to setup an auto scaler, but I am getting the following dependency error:
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. clearml-agent 1.5.0rc0 requires attrs<20.4.0,>=18.0, but you have attrs 22.1.0 which is incompatible.My requirements.txt file has attrs==20.3.0
The tested task was cloned from a task that was finished successfully in a machine running the clearml-agent in docker mode with the same docker image as the autoscaler.
I

  
  
Posted one year ago
Votes Newest

Answers 19


Hi, AgitatedDove14

How do I set the version to 1.5.1,? When I launch the autoscaler the version 1.5.0 is picked by default.

  
  
Posted one year ago

Hmm let me check first when it is going to upgraded and if there is a workaround

  
  
Posted one year ago

Any chance there is an env variable you set to get 1.5.0rc0? Because this is the version that is being used

  
  
Posted one year ago

Hmm how do you launch the autoscaler, code?

  
  
Posted one year ago

AgitatedDove14 , here follows the full log:

  
  
Posted one year ago

Actually, this error happens when a launch the autoscaler from the Web UI, when I enqueue a task, it launches an EC2 instance which "Status Check" stays in "Pending" for over 15 minutes and then the instance is terminated by the scaler that launches another one in a loop.

  
  
Posted one year ago

SkinnyPanda43 I've identified the reason for the forced RC version - we'll remove this constraint and I'll ping you here when you can try again

  
  
Posted one year ago

Hi SkinnyPanda43
This issue was fixed with clearml-agent 1.5.1, can you verify?

  
  
Posted one year ago

SkinnyPanda43 can you please try agent v1.5.1rc0 and let me know if it changes anything?

  
  
Posted one year ago

Based on what I see when the ec2 instance starts it installs the latest, could it be this instance is still running?

  
  
Posted one year ago

SuccessfulKoala55 , how do I set the agent version when creating the autoscaler?

  
  
Posted one year ago

Basically, I am following the steps in this video:
https://www.youtube.com/watch?v=j4XVMAaUt3E

  
  
Posted one year ago

Hi @<1523701875835146240:profile|SkinnyPanda43> , sorry for the delay, we're just in the process of upgrading this in app.clear.ml

  
  
Posted one year ago

Hi @<1523701875835146240:profile|SkinnyPanda43> , it should be OK now - please try it out and let me know

  
  
Posted one year ago

Hi, any update on that?

  
  
Posted one year ago

I am launching through the UI, "XXX workspace / https://app.clear.ml/applications / AWS Autoscaler".

  
  
Posted one year ago

Hi SkinnyPanda43
Can you attache the full log?
Clearml agent is installed before your requirements.txt , at least in theory it should not collide

  
  
Posted one year ago

I think not, I have not set any ENV variable. Just went to the web UI, added an autoscaler, filled the data in the UI and launched the autoscaler.

By inspecting the scaler task, it is running the following docker image: allegroai/clearml-agent-services-app:app-1.1.1-47

  
  
Posted one year ago

So It could be launched by the clearml cli? I can also try that.

  
  
Posted one year ago