{"version":"2.1.247","anchor":"memory-sync-warns-when-fetched-content-does-not-match-its-re","canonical_anchor":"memory-sync-warns-when-fetched-content-does-not-match-its-re","heading":"Memory sync warns when fetched content does not match its recorded digest","tier":"internal","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/memory-sync-warns-when-fetched-content-does-not-match-its-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Memory sync warns when fetched content does not match its recorded digest\n\nMemory sync now warns when fetched content does not match the digest recorded for it.\n\n**What**\n\nThe sync result now carries counts of digest mismatches and restored empty files, and a warning is logged when fetched bodies did not match the digest recorded for them. Such content is filed under the digest actually computed rather than the one claimed.\n\n**Evidence**\n\n`read body\/bodies did not match their declared sha256; recorded under the computed sha`\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}