MetaMask / MetaMask/metamask-extension
ci - `Set up` job fails intermittently with error `Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing`
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
### What is this about?
Error: Action `'https://api.github.com/repos/MetaMask/action-checkout-and-setup/tarball/1024bb1a16f282b4859a714e819f218ffde589c8'` download has timed out. Error: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
It fails 3 times, as this job seems to already have retrials in place
Example of the failure here: https://github.com/MetaMask/metamask-extension/actions/runs/17998342717/job/51202141569
### Scenario
_No response_
### Design
_No response_
### Technical Details
_No response_
### Threat Modeling Framework
_No response_
### Acceptance Criteria
_No response_
### Stakeholder review needed before the work gets merged
- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)
### References
_No response_
Contributor guide
Research direction
Start with the Set up job in the workflow and the referenced MetaMask/action-checkout-and-setup action, then review the example Actions run for the timeout pattern. Determine a reproducible mitigation for the tarball download failure and verify that the job completes without the intermittent 100-second timeout across repeated runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100