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
Looking at the code, it seems that the branch managing the cache not hit in restore.ts doesn't set output before returning:
if (!cacheKey) {
const message = `Cache not found for input keys: ${[
primaryKey,
...restoreKeys
].join(", ")}`;
if (isCacheRequired()) {
throw new Error(message);
} else {
core.info(message);
// I expected to have an utils.setCacheHitOutput(false); here
return false;
}
}
I may be missing something here, If right I can write you the PR.
Thanks !
The text was updated successfully, but these errors were encountered:
This probably works properly since most people use steps.cache.outputs.cache-hit != 'true' as a check rather than checking for false, and the default should be blank (falsey). Still for clarity I agree it would be better for that line to be in there. Are you still willing to make a PR for the change?
Hi !
Looking at the code, it seems that the branch managing the cache not hit in restore.ts doesn't set output before returning:
I may be missing something here, If right I can write you the PR.
Thanks !
The text was updated successfully, but these errors were encountered: