-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue: Cache service responded with 404 with actions/setup-node@v2 #1034
Comments
Hi @aib, |
See also this comment for a solution to disable cache in the |
Ahh, I see. Thanks. |
Hey guys! I was able to use
in This also works great with Cheers 🍻 |
Would it be possible to integrate this directly into act? |
I would have, but I don't speak GO 😔 |
(I'm skipping the issue template since this looks more like an oversight or missing feature than a bug.)
actions/setup-node@v2
, when run withcache: npm
, fails with "::error::Cache service responded with 404".To replicate, one can clone https://github.com/aib/act-setup-node-test and run
act --artifact-server-path /tmp/act-artifacts -j test
. Edit: Or use the following workflow file:Tested against release v0.2.25 and current master.
The requested URL looks like
https://127.0.0.1:34567/_apis/artifactcache/cache?keys=node-cache-Linux-npm-4ae58fb93f5d99af5b6b62d6ba7d42110a267626bfc1d6847922d9e6863ef729&version=b3f0cb83629d634645a5146420c017462ebb5229bd60271a7a86e489a6066469
and seems to be generated by https://github.com/actions/toolkit/blob/main/packages/cache/src/internal/cacheHttpClient.ts#L33 .A workaround is returning HTTP 204 to the request. An actual caching implementation should be easy, too, but I'm not familiar enough with act, GitHub Actions or even Go to submit a PR. (And in any case I'd need an issue # to reference)
The text was updated successfully, but these errors were encountered: