saveourtool/save-cloud

Support the global timeout for executions

Open

#764 opened on May 16, 2022

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)Kotlin (4 forks)github user discovery
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (38 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

We should have a timeout between the start of the execution and the end of it. After we have assigned executionId we should start a timer and mark the execution as timed-out if it was waiting for a long time.

Contributor guide

Research direction
Study the execution lifecycle and add a timeout mechanism using a timer after assigning executionId.
Tech stack
java
Domain
backendcloud
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75