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
Clearml Version 1.8.1 Had "Fix" For The Deferred Init Which Introduces A Bug Btw, I'Ve Opened

⚠️ ClearML version 1.8.1 had "fix" for the deferred init which introduces a bug btw, I've opened None to highlight this.

  
  
Posted one year ago
Votes Newest

Answers 4


Oh this is so internally, the background thread can signal it is not deferred, are you saying there is bug or the code is odd?

  
  
Posted one year ago

I'm saying it's a bug

  
  
Posted one year ago

@<1523701205467926528:profile|AgitatedDove14> this

  
  
Posted one year ago

The deferred_init input argument to Task.init is bool by default, so checking type(deferred_init) == int makes no sense to begin with, and is altering the flow.

  
  
Posted one year ago
597 Views
4 Answers
one year ago
one year ago
Tags