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
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)

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)

Posted 4 months ago
Votes Newest

Answers 4

Hi HugeArcticwolf77 , did you spin new agent versions? What did you have before and what do you have now? Can you check if you revert to the previous version it works out?

Posted 4 months ago

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 4 months ago

HugeArcticwolf77 , what if you specify the exact python binary from conda using CLEARML_AGENT_SKIP_PIP_VENV_INSTALL?

Posted 4 months ago

CostlyOstrich36 it worked! thank you so much :grinning_face_with_star_eyes:

Posted 4 months ago
4 Answers
4 months ago
4 months ago