Cache restore failed with symlinks in Windows
See original GitHub issueI’m working with a monorepo containing several npm packages. The root npm package.json references children npm packages using relative path. When npm ci
/ npm i
is executed, a symlink is created for each child package to the root node_modules
folder.
I cached the root node_modules
folder.
The first workflow run is good, here are the steps:
- Cache restore miss
- Run npm ci
- Run npm build
- Success
- Cache save
The second run is no good:
- Cache restore hit
- Skip run npm ci
- Run npm build
This is only happening in windows-latest environment. I tried to reproduce the issue locally and found out that tar did not recreate the symlinks.
Any guidance on how to proceed?
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
The following package(s) have broken symlinks into the cache
As I played a lot with the cache, I got this message: The following package(s) have broken symlinks into the cache: .
Read more >Git symbolic links in Windows - Stack Overflow
Ignore these Windows symbolic links by adding an entry into file .git/info/exclude. I have not implemented this, but I believe this is a...
Read more >How to restore a symlink repository? - Duplicacy Forum
All my backups use the symlink-repository pattern, and on windows a symlink can only be created with admin ... Restore fails due to...
Read more >How does Windows 7 Backup treat symbolic links?
Backup actually resolves the symbolic link and takes a copy of the data in the ... answer is this one: Perform a backup,...
Read more >Symbolic Link, Reparse Point, and Unsupported file type ...
Symptoms. When backing up a source which contains reparse points you may receive an error: Unsupported file-type skipped. Please see the unsupported log...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@ordian and possibly others with the same symptoms:
I have no idea about the symlink issues discussed here, but your issue looks like #198 and it has a solution.
This issue was closed because it has been inactive for 5 days since being marked as stale.