{"version":"2.1.223","anchor":"config-save-survives-a-failing-stale-write-stat","canonical_anchor":"config-save-survives-a-failing-stale-write-stat","heading":"Config save survives a failing stale-write stat","tier":"notice","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/config-save-survives-a-failing-stale-write-stat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Config save survives a failing stale-write stat\n\nAn unreadable config file no longer aborts saving your settings.\n\n**What**\n\nAn unreadable config file can no longer abort a config save.\n\n**Details**\n\n- During stale-write detection under the config lock, a failing stat used to be rethrown unless it was ENOENT.\n- It is now swallowed and logged instead.\n\n**Evidence**\n\n`Config stale-write stat failed: `\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}