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
Unanswered
There Seems To Be A Quirk In The Behaviour Of

There seems to be a quirk in the behaviour of clearml-session
when running clearml-session all the arguments get stored as future defaults in ~/.clearml_session.json Most of the CLI flags take a value following the flag (e.g. --user or --vscode-server ) HOWEVER --skip-docker-network is a switch, meaning it's a boolean and takes no arguments afterwards That means if I run session with --skip-do ker-network just once, "skip_docker_network": true will get written in the ~/.clearml_session.json and there is no way to change that with CLI Next run will have "skip_docker_network": true no matter what The user can fix that by changing the ~/.clearml_session.json directly with a text editor, but that's hacky. A better way would be to enable such behaviour with CLI
I propose two solutions:
changing the --skip-docker-network from a switch to a flag, which introduces backward incompatibility adding --unskip-docker-network switch. This however introduces inconsistency

  
  
Posted 2 years ago
Votes Newest

Answers

665 Views
0 Answers
2 years ago
one year ago
Tags