Timeout support for Orquesta tasks
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
I have found missing the implementation of timeout logic for the Orquesta tasks.
It would be really nice to have something like this:
...
tasks:
my_task:
action: mypack.myaction
retry:
delay: 10
count: 3
timeout: 120
next:
- when: <% timedout() %>
do: task_for_managing_timeout
...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Orquesta task execution and retry handling used by the YAML task definition. Review how task conditions are evaluated, then determine the expected timeout behavior and how the timedout() condition should report completion. Done means timeout configuration and the shown follow-up task behavior are supported and tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100