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! I'M Trying To Test The (Unpublished) Feature That Should Help Me To Deal With Running Cloned Pipelines From Different Commits/Branches. I Found This Commit:

Hello! I'm trying to test the (unpublished) feature that should help me to deal with running cloned pipelines from different commits/branches. I found this commit: https://github.com/allegroai/clearml/commit/bf9ec770c6fd1b94b66e0750688b2325cc45f7fc
And wanted to build a version from it. I added git+ https://github.com/allegroai/clearml.git@bf9ec770c6fd1b94b66e0750688b2325cc45f7fc#egg=clearml to my requirements.txt but while running the pipeline, I got
Requirement already satisfied: clearml from git+ in /root/.clearml/venvs-builds/3.6/lib/python3.6/site-packages (0.17.5)Any suggestions to help? Or expected ETA for the next version with this code?

  
  
Posted 3 years ago
Votes Newest

Answers 5


Hi CleanPigeon16
Put the specific git into the "installed packages" section
It should look like:
... git+ ...(No need for the specific commit, you can just take the latest)

  
  
Posted 3 years ago

Hooray! That works AND the feature works!
Quick follow up question, is there any way to abort a pipeline and all of the tasks it ran?

  
  
Posted 3 years ago

That works AND the feature works!

YEY

Quick follow up question, is there any way to abort a pipeline and all of the tasks it ran?

Hmm yes currently if you abort the pipeline is has no "time" to abort the running Tasks (the DAG itself will stop, because the pipeline controller was aborted, bit the running Tasks will continue).
In order to have better support, we need to add a previously requested feature for "abort" callback. This is actually not as straight forward as it sounds.
The plan is to get the pipeline for the next version (this includes improved callbacks and automatic step reuse), then for the version after that, to add the abort callback.
wdyt?

  
  
Posted 3 years ago

Sounds promising, any ETA for the next version?

  
  
Posted 3 years ago

There is a version coming out next week, the one after it (probably 2/3 weeks later) will have this feature

  
  
Posted 3 years ago
1K Views
5 Answers
3 years ago
one year ago
Tags