Cache Service Url not found, unable to restore cache
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Using the cache package identically as the actions/cache@v2 action it breaks with
Error: getCacheEntry failed: Cache Service Url not found, unable to restore cache.
at /home/runner/work/benchmark/benchmark/node_modules/@actions/cache/src/internal/requestUtils.ts:92:9
at Generator.next (<anonymous>)
at fulfilled (/home/runner/work/benchmark/benchmark/node_modules/@actions/cache/lib/internal/requestUtils.js:5:58)
Why are the ACTIONS_CACHE_URL ACTIONS_RUNTIME_URL only available in the action? Who magically injects them and when?
If this is not a bug, is this page meant to be used exclusively within the Github action and never on its own?
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 cache package's requestUtils.ts at the reported line and compare its runtime assumptions with actions/cache@v2. Trace how ACTIONS_CACHE_URL and ACTIONS_RUNTIME_URL are supplied in GitHub Actions, then determine whether standalone use is supported. Done means the expected behavior and any required documentation or fix are established.
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
- 25/100