Sankalp Kotewar

@airtonix do you want to create a PR by updating this in the readme docs so that we can have more eyes on this?

Closed due to no reply. Feel free to reopen this issue if you feel this needs to be addressed. I tried a sample workflow with normal golang code but didn't...

Hi @younke, thanks for your contribution. We have kept `restore-key` in examples for everyone to understand how the templates would look by default. Your recommendation looks more like a good...

Closing this PR as there is no response. But to make this clearer, the readme will be updated by giving better insights on `cache-hit` and partial match `restore-key`. PR raised...

Hi there, 👋🏽 We have released a new `actions/cache` version `v3.0.7` that doesn't run the stuck runner for 6 hours, instead aborts the download and gets out of the cache...

@asottile-sentry, we are working on making it configurable to the user so that everyone can set their own timeouts... Hope that works? Also we're tracking this issue [here](https://github.com/actions/cache/issues/810), hence closing...

We suspect an issue with the Azure SDK and we've opened an issue for the same here - https://github.com/Azure/azure-sdk-for-js/issues/22321

Hi all, We have released a new `actions/cache` version `v3.0.7` that doesn't run the stuck runner for 6 hours, instead aborts the download and gets out of the cache restore...

Hi @Kurt-von-Laven 👋🏽 For now we've set it to one hour as we didn't want any customer to face issue in case their self hosted runner runs on a low...

Hi everyone! We have introduced an [environment variable](https://github.com/actions/cache#environment-variables) `SEGMENT_DOWNLOAD_TIMEOUT_MINS` to configure the timeout for the [download of the cache segment](https://github.com/actions/cache#cache-segment-restore-timeout). This way you won't have to wait for 1 hour...