Cache not being hit despite of being present
See original GitHub issueIn this ticket, the user use the cache action to cache some dependencies. At the first time to run this action in the workflow , it will returns that Cache not found for input keys
, and then the cache will be saved with the specified key
in the Post
cache step, this is correct behavior as expected.
However, when run the action next time, it still reports that Cache not found for input keys
, the key is same as the first time.
I tested and tried as the demo shared by this user, but I did not reproduce the problem.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Actions/cache: Cache not being hit despite of being present
Not on the branch. And in my experience, it only gets a cache hit on the same commit when I re-run the workflow....
Read more >Cache Miss – What It Is and How to Reduce It - Hostinger
Cache miss suggests that requested data is not available in cache memory. Read on to learn how to reduce them and make the...
Read more >When They Occur (& How to Increase Cache Hit Ratio)
Learn why it is important to have a caching policy, when cache miss and cache hit occur, how cache hit ratio is calculated...
Read more >What's a Cache Miss? Policies That Reduce ... - Hazelcast
A cache miss occurs when a system or application makes a request to retrieve data from a cache, but that specific data is...
Read more >Why isn't Chrome caching responses, even when cache ...
I've ensured that Cache is enabled (i.e. "Disable Cache" in unchecked). When I refresh the page, the call for 167281/ gets made again....
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
Hello, and apologies for the late reply @joshmgross. I wasn’t aware of the scoping of the builds across different branches. If that’s expected behavior, we are working fine!
However, I’d still like to request you to make this point a little more prominent in the docs/README.
Thanks for your reply!
#307 has added this detail to the main README with a link to the help docs for more details.
Thank you all for the feedback!