Wrong Cache restore operation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
When trying to restore the "cache-toolchains-atf-d64" the Cache action actually restores "cache-toolchains-atf-d64x" (with 'x' at the end):
Run actions/cache/restore@v3
with:
path: /work/atf_toolchains
key: cache-toolchains-atf-d64
enableCrossOsArchive: false
fail-on-cache-miss: false
lookup-only: false
...
Cache restored successfully
Cache restored from key: cache-toolchains-atf-d64x
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 reproducing the workflow using actions/cache/restore@v3 with the logged path and key, then inspect why the requested cache-toolchains-atf-d64 resolves to cache-toolchains-atf-d64x. No source file or test is named in the issue; done means the restore operation returns the exact requested key, with a regression test or reproduction confirming the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100