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
Hello Again! Also Wanted To Ask About

Hello again! Also wanted to ask about custom_build_script argument in clearml.conf . Can somebody point me in the direction of a working example of such script that may be used instead of installing a virtual environment? I couldn't find any info about it except what is in the config comments. At this point it's not completely clear to me what should be inside, and whether it should produce json file using CLEARML_CUSTOM_BUILD_OUTPUT environment variable or it should create this variable in the first place. Again, thanks in advance!

  
  
Posted 2 years ago
Votes Newest

Answers 8


Hi BurlyRaccoon64
What do you mean by "custom_build_script" ? not sure I found it in "clearml,conf"
https://github.com/allegroai/clearml-agent/blob/master/docs/clearml.conf

  
  
Posted 2 years ago

And right now I am on 1.3.0 version

  
  
Posted 2 years ago

Hmm
CLEARML_CUSTOM_BUILD_OUTPUT
This might be an enterprise feature, I'm not aware of anything in the open source version

  
  
Posted 2 years ago

AgitatedDove14 Thanks for your help anyway!

  
  
Posted 2 years ago

My pleasure 🙂
I do not think it should change anything, just pull the latest agent and reinstall
pip3 install -U clearml-agent

  
  
Posted 2 years ago

My previous version was 1.2.4rc3, but to be honest, I can't find this part of the config in the corresponding commit as well

  
  
Posted 2 years ago

At some point I was installing it from an unstable release, and probably that is when this part was added to the config but it didn't get to the proper release after that

  
  
Posted 2 years ago

I have these lines in my clearml.conf file. I can't find it on GitHub as well but in release notes it says that it was added in v1.2.1 https://github.com/allegroai/clearml-agent/releases/tag/v1.2.1
# Specifies a custom environment setup script to be executed instead of installing a virtual environment. # If provided, this script is executed following Git cloning. Script command may include environment variable and # will be expanded before execution (e.g. "$CLEARML_GIT_ROOT/script.sh"). # The script can also be specified using the CLEARML_AGENT_CUSTOM_BUILD_SCRIPT environment variable. # # When running the script, the following environment variables will be set: # - CLEARML_CUSTOM_BUILD_TASK_CONFIG_JSON: specifies a path to a temporary files containing the complete task # contents in JSON format # - CLEARML_TASK_SCRIPT_ENTRY: task entrypoint script as defined in the task's script section # - CLEARML_TASK_WORKING_DIR: task working directory as defined in the task's script section # - CLEARML_VENV_PATH: path to the agent's default virtual environment path (as defined in the configuration) # - CLEARML_GIT_ROOT: path to the cloned Git repository # - CLEARML_CUSTOM_BUILD_OUTPUT: a path to a non-existing file that may be created by the script. If created, # this file must be in the following JSON format: # ```json # { # "binary": "/absolute/path/to/python-executable", # "entry_point": "/absolute/path/to/task-entrypoint-script", # "working_dir": "/absolute/path/to/task-working/dir" # } # ``` # If provided, the agent will use these instead of the predefined task script section to execute the task and will # skip virtual environment creation. # # In case the custom script returns with a non-zero exit code, the agent will fail with the same exit code. # In case the custom script is specified but does not exist, or if the custom script does not write valid content # into the file specified in CLEARML_CUSTOM_BUILD_OUTPUT, the agent will emit a warning and continue with the # standard flow. custom_build_script: ""

  
  
Posted 2 years ago
951 Views
8 Answers
2 years ago
one year ago
Tags