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 clearml :slightly_smiling_face: I am having a small problem with `clearml-agents` mainly related to: _private repository, cache and vcs._ I am using the latest version `clearml-agents==1.5.2rc` on _python 3.10 (ubuntu:22.04_). I am running a `scri

Hello clearml 🙂
I am having a small problem with clearml-agents mainly related to: private repository, cache and vcs. I am using the latest version clearml-agents==1.5.2rc on python 3.10 (ubuntu:22.04 ).

I am running a script_a.py from a private_repo_a that also depends on private_repo_b . The script_a is launched from a service in such a way:

my_task= Task.create(
    project_name="My project",
    task_name="My task",
    repo="private_repo_a"
    script="script_a.py",
    branch="dev",
    requirements_file="requirements.txt",
    )
Task.enqueue(task=my_task.id, queue_name="default")

If I push new changes (e.g. commit_2 ) on script_a or in private_repo_b the clearml-agents still keep the previous commit.
To make it read the latest commit (e.g. commit_2 ), I open the clearml-agents machine, stop the agent, clear the cache ( ~.clearml ). it then works.

I have tried pretty much to set in the clearml-conf all these configurations:

pip_download_cache : {enabled: false, ... }
vcs_cache: { enabled: false, ...}

and finally this
venvs_cache: {max_entries: 0, ...}

but I still have this behaviour. the only way to make it is to clear the cache. Anything I am missing? Could you help me with that? thanks a lot !!! 🙂

  
  
Posted one year ago
Votes Newest

Answers 2


Hey @<1574207113163444224:profile|ShallowCoyote86> , what exactly do you mean by "depends on private_repo_b "? Another question - after you push the changes, do you re-run script_a.py ?

  
  
Posted one year ago

Hey @<1537605940121964544:profile|EnthusiasticShrimp49> 🙂

sorry I was not clear, with depends on private_repo_b , I meant in the requirement.txt I have something like

private_repo_b @ 

After my changes, I try to launch the script_a again either from a Task.create() syntax or even with task.execute_remotely()

in both cases it seems to re-use the older version of dev or the branch I am in. I looked into the log and even it finds a new commit, it seems to install the older one. not sure why.

  
  
Posted one year ago
776 Views
2 Answers
one year ago
one year ago
Tags
Similar posts