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
Hi, Was There Any Change In Clearml-Agent Recently That Caused It To Ignore The Environment Variable $Clearml_Agent_Skip_Pip_Venv_Install? I Had To Spin New Agents And Now They Try To Create Venv For No Reason ( The Environment Already Exists)


CostlyOstrich36 ok the issue is not the clearml-agent version, it is the conda environment I'm trying to run with. I usually run my agents from one conda environment and when I pass CLEARML_AGENT_SKIP_PIP_VENV_INSTALL=1, it just uses the conda interpreter and all is good. When I try to do this with a different conda env, this does not work and tries forcibly to create a new venv. any idea why?

Edit: if it is any help, the conda env that works is installed in the conda install dir, and the not-working conda env is installed on a different local disk.

Digging through the log, this is the main difference:
This is an example of a good detection of current conda env:
Interpreter 'python3.8' found at '/home/USERNAME/miniconda3/envs/torch/bin/python3.8'

and this is a bad example:
Interpreter 'python3.8' found at '/usr/bin/python3.8'

This is bad since the python interpreter in the second conda env is python3.9 and not 3.8. This is despite the fact that agent.default_python=3.9 which is the correct version.

  
  
Posted one year ago
206 Views
0 Answers
one year ago
one year ago