question-mark
Stuck on an issue?

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.

can NOT find cache

See original GitHub issue

Description: I created branch node-cache-3 from branch node-cache. It means the branch node-cache-3 has the base branch node-cache, doesn’t it? In github docs, a branch can access to caches if its base branch creates caches.

A workflow can access and restore a cache created in the current branch, the base branch (including base branches of forked repositories), or the default branch (usually main). For example, a cache created on the default branch would be accessible from any pull request. Also, if the branch feature-b has the base branch feature-a, a workflow triggered on feature-b would have access to caches created in the default branch (main), feature-a, and feature-b.

link: https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows#restrictions-for-accessing-a-cache

The branch node-cache-3 can NOT access to caches even if node-cache creates its caches in my repository.

link: https://github.com/guppy0356/gh-actions/runs/7296326981?check_suite_focus=true link: https://github.com/guppy0356/gh-actions/runs/7296402979?check_suite_focus=true

Action version: Specify the action version

Platform:

  • Ubuntu
  • macOS
  • Windows

Runner type:

  • Hosted
  • Self-hosted

I can’t understand runner type is.

Tools version:

yarn 1.22.19 node v16.15.1

Repro steps:

    - name: Use Node.js
      uses: actions/setup-node@v3
      with:
        node-version: 18
        cache: 'yarn'

Expected behavior: The branch node-cache-3 can access to caches created in the its base branch (node-cache).

Actual behavior: The branch node-cache-3 can NOT access to caches created in the its base branch (node-cache).

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:16 (5 by maintainers)

github_iconTop GitHub Comments

2reactions
guppy0356commented, Jul 12, 2022

@vsafonkin

no, no, no. please don’t close this. The caches created in base branch has NOT been accessible.

0reactions
guppy0356commented, Aug 4, 2022

@dmitry-shibanov I’ve posted https://github.com/actions/cache/issues/877. I found documentation is wrong. Thank you for your cooperation.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Cannot find cache named '' for CacheableOperation[] caches
Try this : @Bean public CacheManager cacheManager() { SimpleCacheManager cacheManager = new SimpleCacheManager(); List<Cache> caches = new ...
Read more >
Cannot find cache named config - eDelivery User Community -
Caused by: java.lang.IllegalArgumentException: Cannot find cache named 'config' for Builder[public java.util.
Read more >
Caching with Ehcache 3.10.0 in Spring Boot 2.7.0 does not work
IllegalArgumentException : Cannot find cache named 'myKey' for Builder[public java.lang.String com.example.demo.ServiceWithCaching.
Read more >
Cache named[users] not found error - Google Groups
In your applicationContext. xml only defaultCache is defined (cacheName property in CacheFactory).
Read more >
CacheManager/java.lang.InstantiationException: Cannot find ...
Symptom. This solution is to understand the root cause for the CacheManager/java.lang.InstantiationException: Cannot find the cache definition ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found