You could hang committable and benchable for a really long time by sleeping for the max timeout for the max number of commits
Open
Nobody has claimed this yet.
all bots
testneeded
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
It would be good to have a timer around the loop that runs the code for each commit so we can bail out if the total time is taking too long, in addition to the alarm-based timeout for each individual run.
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 at the entry point that loops over commits and runs the code, then inspect how the existing alarm-based timeout is applied to each individual run. Define and add a total elapsed-time limit for the commit loop so it stops processing when the overall work takes too long.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100