René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Action should pretend a \"cache miss\" on networking issues","articleBody":"**Description:**\r\nUnderlying infrastructure issue for GitHub artifacts cause a lot of issues for workflows depending directly or indirectly on actions that use the caching infrastructure from `actions/toolkit`. See https://github.com/actions/cache/issues/820 for details.\r\n\r\nI would highly suggest that this action should be more resilient regarding service outages in the backing caching infrastructure.\r\n\r\nThe issues of today would most probably not be visible if the cache action would do \"nothing\" (like a cache miss) when the caching backend can't be reached or the server responds with an incorrect answer.\r\n\r\nThe `@actions/cache` action does show how a resilient implementation can look like: https://github.com/actions/cache/blob/main/src/restore.ts#L55\r\n\r\nCurrently there is now exception catching done in the `@actions/setup-java` action: https://github.com/actions/setup-java/blob/main/src/cache.ts#L90\r\n\r\n**Justification:**\r\nIt is unacceptable that problems with GitHub caching/artifact infrastructure will effectively make most workflows unusable.","author":{"url":"https://github.com/foxylion","@type":"Person","name":"foxylion"},"datePublished":"2022-06-13T15:05:55.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/344/setup-java/issues/344"}