-
Notifications
You must be signed in to change notification settings - Fork 1.3k
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Cache validation for symblic-linked path failed since v3.7.0 #806
Comments
Hello @kyontan ! Thank you for reporting the issue, we will take a closer look and see what can be done :) |
Hello @kyontan. We've merged the pull request with possible fix. Could you please try to use For now I'm going to reopen the issue. |
Hi @dmitry-shibanov, Our team confirmed that the fix in |
Hello @kyontan. The new version of setup-node was released. For now I'm going to close the issue. If you have any concerns feel free to ping us. |
Description:
Since v3.7.0, the workflow using
actions/setup-node
started failing for the error described below.Our repository uses symblic link for some reason, and v3.7.0 had revised cache resolution logic so that I think this is a kind of regression for the change around:
setup-node/src/cache-utils.ts
Lines 144 to 152 in e33196f
I've not confirmed the cause, but I expect that the line
.filter(directory => fs.lstatSync(directory).isDirectory());
drops symblic linked.Action version:
v3.7.0
Platform:
Runner type:
Tools version:
Repro steps:
A description with steps to reproduce the issue. If you have a public example or repo to share, please provide the link.
Setup repository like following structure:
workflow file:
Expected behavior:
A description of what you expected to happen.
The 2nd
actions/setup-node@v3
step succeeds.Actual behavior:
The 2nd
actions/setup-node@v3
step fails for the error:The text was updated successfully, but these errors were encountered: