-
Notifications
You must be signed in to change notification settings - Fork 27
Fails by simply dumping the script #30
Comments
I think this time it is a permission issue. Whatever the issue, the real issue is that gcs-cache-action is not surfacing these errors. |
I had it working for a while, but then it started failing with the same dump of script, and I have no clue how to debug it. @basilenouvellet any chance there is a quick fix for error reporting? |
I am not familiar with GitHub actions SDK, but it looks like all we are missing is some sort of try..catch here: https://github.com/MansaGroup/gcs-cache-action/blob/main/src/post.ts#L47 |
I will take a look tomorrow to add some error checking, sorry about that! |
Thanks a lot for publishing this action. Saved a ton of time! |
Hi @gajus, I've pushed on |
@IamBlueSlime Could you please publish this under 1.0.3 tag? |
@gajus Did you test the main branch? To not publish a version which does not work :) |
I cannot. Our CI agents are configured not to allow untagged actions. It has to have a version tag in semver form and a hash. I can try to replicate it on a public repository if that helps, though that won't be an accurate test. |
Fair enough, I will publish a pre-release ASAP, if it still blocked I will publish a real one |
Here is how we have it setup:
Here is how it fails:
The text was updated successfully, but these errors were encountered: