{"version":"2.1.228","anchor":"cache-read-failures-no-longer-propagate-to-the-caller","canonical_anchor":"cache-read-failures-no-longer-propagate-to-the-caller","heading":"Cache read failures no longer propagate to the caller","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/cache-read-failures-no-longer-propagate-to-the-caller","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Cache read failures no longer propagate to the caller\n\nPull-request and closed-issue cache read errors no longer break the thing loading them.\n\n**What**\n\nReads from the pull-request status cache and the closed-issues cache are wrapped so a storage error is logged and an empty result returned, instead of throwing out of the loader.\n\n**Details**\n\n- Expected errors and genuine faults take different logging paths; the closed-issues failure log names the underlying error.\n\n**Evidence**\n\n`closed-issues cache read failed: ${i}`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}