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
Why Would Every Submitted Task Be Aborted Directly?

Why would every submitted task be aborted directly?

  
  
Posted 2 years ago
Votes Newest

Answers 13


TenseOstrich47 , what do you mean exactly? Every task you run ends on 'aborted' status?

  
  
Posted 2 years ago

It should be a draft, so that it can be enqueued

  
  
Posted 2 years ago

TenseOstrich47 , can you please describe what your usage is?

  
  
Posted 2 years ago

Ok, that explains a lot. The new user was using version 1.x.x and I was using version 0.17.x. That is why I think my task was being drafted. and his was being aborted.

There is no specific use case for draft mode - it was just the mode I knew that I understood to be used for enqueuing a newly created task, but I assume that aborted now has the same functionality

  
  
Posted 2 years ago

Any specific use case for the required “draft” mode?

Nothing except that Draft makes sense feels like the task is being prepped and Aborted feels like something went wrong

  
  
Posted 2 years ago

Nothing except that Draft makes sense feels like the task is being prepped and Aborted feels like something went wrong

Yes guess that if we call execute remotely, without a queue, it makes sense for you to edit it...
Is that the case TrickySheep9 ?
If it is I think we should change it to draft when it is not queued. sounds good to you guys ?

  
  
Posted 2 years ago

Any specific use case for the required "draft" mode?

  
  
Posted 2 years ago

I was having this confusion as well. Did behavior for execute_remote change that it used to be Draft is Aborted now?

  
  
Posted 2 years ago

Yep that makes sense to me too. Done

  
  
Posted 2 years ago

I was having this confusion as well. Did behavior for execute_remote change that it used to be Draft is Aborted now?

Actually it was changed, it used to reset the Task (then push into into execution queue if needed), with clearml v1.0, we now support pushing aborted Tasks back into queues, so execute_remotely aborts the Task (instead of reseting it)
(you can always manually reset it)

  
  
Posted 2 years ago

Yeah sounds good to me

  
  
Posted 2 years ago

Not that I know of... Is there an agent waiting on the queue? If so, can you try without an agent listening on the queue?

  
  
Posted 2 years ago

New user is trying to push tasks, and the task is instantly changed to aborted from running

  
  
Posted 2 years ago
533 Views
13 Answers
2 years ago
one year ago
Tags