You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Though seems current behaviour is potentially worse than how it was back with original issue. Current behaviour is project B cache is never considered for project A artifacts meaning when the artifacts go out of cache for project A, they will never be considered cached.
This makes a junction use the artifact cache of the parent project
before the ones defined for the junction
This was originally done in 24c0de1,
but regressed at some point
Fixes#1839
This makes a junction use the artifact cache of the parent project
before the ones defined for the junction
This was originally done in 24c0de1,
but regressed at some point
Fixes#1839
Opening a new issue, this has regressed #401
Same reason as before. If project A is popular, this will literally kill the cache server.
The text was updated successfully, but these errors were encountered: