Flaky connections
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.9k
- Forks
- 2.8k
- PR merge metrics
- No merged PRs in 30d
Description
We're experiencing extreme flakiness trying to check out our own repo in our CI and deploy suites. We're running Github actions hosted at Github and a Github repo hosted at Github.
This is the first step in our job:
steps:
- uses: actions/checkout@v4
It hangs until the workflow or job times out.
The specific command that it hangs on is the last step of the action --
/usr/bin/git -c protocol.version=2 fetch --prune --no-recurse-submodules origin +refs/heads/*:refs/remotes/origin/* +refs/tags/*:refs/tags/*
The debug logs don't show anything interesting. That /usr/bin/git command doesn't ever print anything.
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 with the actions/checkout@v4 step and the reported /usr/bin/git fetch command. Reproduce the timeout in a GitHub-hosted workflow, then inspect the checkout action's handling of this fetch path and its debug output. Done means identifying a reliable cause and a verified fix or mitigation for the hanging checkout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100