Improve job idle timeout logic
- Dominant language
- Python
- Stars
- 133
- Forks
- 205
- Avg merge
- 16h 3m
- Merged PRs (30d)
- 102
Description
### Problem Description
There's a problem reported with jobs being marked as "idle" too soon - original timeout was 1 minute. Now, the timeout was changed to 5 minutes, but it's still hardcoded.
We need to be able to either increase the timeout, or disable it fully.
### Proposed Solution
- Provide configuration option that will determine the timeout.
- If possible, provide log messages that explain why timeout happened and what to do with it
Contributor guide
Research direction
The issue names no files, tests, or entry points. First locate the job idle-timeout implementation and review existing configuration and logging conventions. Done means the timeout can be configured or disabled, and timeout logs explain the cause and next step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100