Adding timeout to prevent overlapping cron jobs
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 8.9k
- Forks
- 715
- PR merge metrics
- No merged PRs in 30d
Description
What about adding timeout on every or job level to prevent overlapping cron jobs?
https://man7.org/linux/man-pages/man1/timeout.1.html
Examples:
every :day, at: '12:20am', timeout: 10.minutes do
rake "app_server:task"
end
every :day, at: '12:20am' do
rake "app_server:task", timeout: 10.minutes
end
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 reviewing the existing every and job-level APIs in Whenever, then read the linked timeout(1) documentation to understand the proposed behavior. Compare the two examples and define how a timeout should prevent overlapping cron jobs; done means the supported scope and behavior are agreed and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, ruby
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100