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
Anyway To Make A Job Fail If The Required Python Version (3.7 Vs 3.8 For Example) Is Not Available In The Agent?

Anyway to make a job fail if the required python version (3.7 vs 3.8 for example) is not available in the agent?

  
  
Posted 2 years ago
Votes Newest

Answers 7


Hmm, we could add an optional test for the python version, and the fail the Task if the python version is not found. wdyt?

  
  
Posted 2 years ago

Won't it be too harsh to have system wide restriction like that ?

  
  
Posted 2 years ago

I would prefer controlled behavior than some available version being used. Here triggered a bunch of jobs that all went fine and even evaluations were fine and then when we triggered a inference deploy it failed

  
  
Posted 2 years ago

then when we triggered a inference deploy it failed

How would you control it? Is it based on a Task ? like a property "match python version" ?

  
  
Posted 2 years ago

Hmm, interesting, why would you want that? Is this because some of the packages will fail?

  
  
Posted 2 years ago

that or in clearml.conf or both

  
  
Posted 2 years ago

In this case, particularly because of pickle protocol version between 3.7 and 3.8

  
  
Posted 2 years ago
760 Views
7 Answers
2 years ago
one year ago
Tags