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
This Message Is For The Clearml Team. I'Ve Found A Bug. I Think It'S Reproducible. Basically, When Dealing With Bools Inside Args, I Think What You Guys Do Is Just Cast It To Bool Since All The Args Are Stored As Strings If I'M Correct. Only Issue Is, Boo

This message is for the ClearML team. I've found a bug. I think it's reproducible. Basically, when dealing with bools inside args, I think what you guys do is just cast it to bool since all the args are stored as strings if I'm correct. Only issue is, bool(string) equals True. even if its bool("False"), that also outputs True.

  
  
Posted 2 years ago
Votes Newest

Answers 13


only issue is even though it's a bool, it's stored as "False" since clearml stores the args as strings.

  
  
Posted 2 years ago

It was nargs="?" I think

  
  
Posted 2 years ago

Basically if I pass an arg with a default value of False, which is a bool, it'll run fine originally, since it just accepted the default value.

I think this is the nargs="?" , is that right ?

  
  
Posted 2 years ago

And casting it to bool converts it to True

  
  
Posted 2 years ago

Yeah

  
  
Posted 2 years ago

(basically python abusing types/casting where the value can be both str/bool on the same argparser aergument)

  
  
Posted 2 years ago

I'll create a github issue. Overall I hope you understand.

  
  
Posted 2 years ago

Basically if I pass an arg with a default value of False, which is a bool, it'll run fine originally, since it just accepted the default value.

  
  
Posted 2 years ago

However when i'll reset or clone the task, now it won't just accept the default value but clearml will pass the arg directly

  
  
Posted 2 years ago

Hi VexedCat68
can you supply more details on the issue ? (probably the best is to open a github issue, and have all the details there, so we have better visibility)
wdyt?

  
  
Posted 2 years ago

I've also mentioned it on the issue I created but I had the issue even when I set the type to bool in parser.add_argument(type=bool)

  
  
Posted 2 years ago

Yep, and this is the root cause of the issue (But easily fixable) 🙂

  
  
Posted 2 years ago

okay thanks! let's pick it up on github 🙂

  
  
Posted 2 years ago
646 Views
13 Answers
2 years ago
one year ago
Tags