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
Is There A Way To Fail Early If A Task In A K8S Pipeline References A Queue That Doesn'T Actually Exist? We'Ve Had This Happen By Accident (Typo), The Pipeline Just Kept Running Indefinitely.

Is there a way to fail early if a task in a k8s pipeline references a queue that doesn't actually exist? We've had this happen by accident (typo), the pipeline just kept running indefinitely.

  
  
Posted one month ago
Votes Newest

Answers 2


Hi @<1798887585121046528:profile|WobblyFrog79> , how did this queue get there? Also, what did you see in the logs?

  
  
Posted one month ago

@<1523701087100473344:profile|SuccessfulKoala55> my colleague submitted a pipeline whose component was referencing a non-existent queue. The queue doesn't actually exist, that's the issue. The "default" queue that handles the controller task just started to output error messages saying that this component can't be scheduled due to missing queue. We just want a way to fail early if a queue doesn't exist, instead of a pipeline running indefinitely without actually failing.

  
  
Posted one month ago
270 Views
2 Answers
one month ago
one month ago
Tags