Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
The cache limit is too small
See original GitHub issueI understand that Issue is not related to the code of this repository, but I would like to discuss with many people, so I open Issue here. (and I know community forums exist. but many people probably don’t know yet.)
First, I really appreciate the GitHub team for adding the cache feature to GitHub Actions. That’s great for us! But, In recent years, node_modules is too large. 200MB can’t cover it. It’s the same in other languages. For example, using esy to install the opam packages, it can easily exceed 800MB. Is there a way to increase the cache limit? or if individual cache limits are removed, it becomes a relatively realistic limit. I know that if the file size is too large, save/restore may insanely slow down. but it shouldn’t be limited on the cache action side.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:121
- Comments:114 (62 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The latest release has bumped the per-cache limit to 2GB to match the per-repo limit https://github.com/actions/cache/releases/tag/v1.1.0
The individual limit has been bumped to 400MB, ensure that you’re pinned to
v1orv1.0.1to get that update. We’re working on increasing it further.