No timeout for stuck command
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
I created a basic ExpressJS server and was using Github Actions for the very first time, and in the jobs, I created two steps, one to install the dependencies: npm install and another to run the server: npm start. And since the command is not producing any output for long, I expect this to be terminated anyhow after a certain timeout. But it is running indefinitely (31 mins and counting).
To Reproduce
Steps to reproduce the behavior:
- Clone this repo
- Try running workflow manually
Expected behavior
Any command which is kinda stuck, which means not producing any output or change should be terminated after a specific period of time. More precisely, there should be a timeout for every command.
Screenshots

If this happens on a number of workflows, it may give birth to downtime for Github Actions.
I've stopped mine 🙂.
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 cloning the repository and running the workflow manually with npm install followed by npm start; observe the command that produces no output. Define and verify timeout behavior for stuck commands, including the expected handling of long-running server processes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100