`Failed to restore: getCacheEntry failed: Cache service responded with 503` when using a fork of actions/cache
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
I need to run a fork of actions/cache because the default timeout values do not play nicely with my caching proxy (it needs to cache the entire file before sending data back in a range request and so it will take longer than the default timeout values)
https://github.com/osy/actions-cache/commit/2fc65ffa9098d26fa9a7be100f1b81a97ff6341a
This had worked for a long time but recently, I get Failed to restore: getCacheEntry failed: Cache service responded with 503 which I suspect is because I am using a fork (pointing to this repo works fine).
Please either fix forking actions/cache or provide us with better control of the timeouts.
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 linked fork commit and compare its actions/cache behavior with the upstream repository, then reproduce the 503 using the proxy setup described in the issue. Done means the fork works reliably with the cache service or the timeout behavior is explicitly controllable and verified against the reported restore failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100