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
Bug: There A Bunch Of Phantom Tasks In A Queue: They Are Archived And In Status Draft. Trying To Remove Them Results In A “Remove Queue Failed” Popup. If I Delete The Task - Then The Queue Entry Becomes Blank, But You Still Cannot Delete It

bug: There a bunch of phantom tasks in a queue: they are archived and in status draft. Trying to remove them results in a “Remove Queue failed” popup. If I delete the task - then the queue entry becomes blank, but you still cannot delete it

  
  
Posted 2 years ago
Votes Newest

Answers 12


I think they appeared when I had a lot of HPO tasks enqueued and not started yet, and then I decided to either Abort or Archive them - I don’t remember already

  
  
Posted 2 years ago

FiercePenguin76 does this happen in a self-hosted ClearML Server? If so, what is the server version?

  
  
Posted 2 years ago

no new unremovable entries have appeared (although I haven’t tried)

  
  
Posted 2 years ago

FiercePenguin76 , we'll try to reproduce. Thanks for the input!

  
  
Posted 2 years ago

but the old ones are there, and I can’t do anything about them

  
  
Posted 2 years ago

And still happens?

  
  
Posted 2 years ago

image

  
  
Posted 2 years ago

log:
[2021-09-09 11:22:09,339] [8] [WARNING] [clearml.service_repo] Returned 400 for tasks.dequeue in 2ms, msg=Invalid task id: id=28d2cf5233fe41399c255950aa8b 8c9d,company=d1bd92a3b039400cbafc60a7a5b1e52b

  
  
Posted 2 years ago

self-hosted. Just upgraded to latest version today (1.1.1). The problem appeared when we were still using 1.0.2

  
  
Posted 2 years ago

this does not prevent from enqueuing and running new tasks, rather an eyesore

  
  
Posted 2 years ago

We'll take a look

  
  
Posted 2 years ago

for the tasks that are not deleted, log is different:
[2021-09-09 12:19:07,718] [8] [WARNING] [clearml.service_repo] Returned 400 for tasks.dequeue in 4ms, msg=Invalid task id: status=stopped, expected=queued

  
  
Posted 2 years ago
575 Views
12 Answers
2 years ago
one month ago
Tags