Fix cache restore bug in gh issue #1377 by fixing paths

[devsh4]

There's an open issue in @actions/toolkit that uncovers a major bug with cache restores not working after v3.1.1 of @actions/cache.

On attempting to upgrade and use v3-s3 of this action, we ran into similar issues and the below PR is to fix the underlying issue until the upstream PR is merged.

Description

• Use .slice() to fix cache paths based on this comment

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (add or update README or docs)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[devsh4]

@whywaita please review.

[devsh4]

@whywaita Were you able to review? I see the check dist CI step failing but assuming it's not related to this PR. Thanks!

[whywaita]

I will review it. But We need to fix CI in this pr.

[whywaita]

@devsh4 Did you write a comment under dist/*.js?

dist directory must generate files from npm run build. We need to write a comment in .ts files if we want to write a comment.

[devsh4]

@whywaita my bad, that was a bad copy/paste and I thought I pushed the commit. Should be good now.

[markandrus]

Previous message

Thanks for this, @devsh4.

Is this fix working for y'all? I pointed my GitHub workflow to your fork to try it, but I still see "not found" failures like this

Cache not found for input keys: v1-Linux-ARM64-8ece81f19f8907841274feda72820220bb97cc28784a63e9ef9b00aea8729635, v1-Linux-ARM64-

even though the "v1-Linux-ARM64-8ece81f19f8907841274feda72820220bb97cc28784a63e9ef9b00aea8729635" does in fact exist in the S3 bucket. I cannot tell if this is the bug or not.

EDIT: Nevermind, I realize I was hitting a different issue, and have opened this PR: whywaita/actions-toolkit-s3#11

[devsh4]

@whywaita any concerns or is this PR good to merge?

[whywaita]

Sorry late. Thank you!