{"version":"2.1.280","anchor":"new-atomic-write-conflict-error-cases-for-staged-tempfiles","canonical_anchor":"new-atomic-write-conflict-error-cases-for-staged-tempfiles","heading":"New atomic-write conflict error cases for staged tempfiles","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/new-atomic-write-conflict-error-cases-for-staged-tempfiles","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### New atomic-write conflict error cases for staged tempfiles\n\nTwo new error cases handle stuck or duplicated temp files during atomic file writes\n\n**What**\n\nThe file-write error mapper gained two new error variants for atomic writes (writes that stage a temporary file before replacing the real one):\n\n- `WORKING_TMP_STUCK` \u2014 the staged temporary file couldn't be removed after being taken back\n\n- `WORKING_NAME_TWINNED` \u2014 the staged temporary file couldn't be removed or taken back, and may now exist as a second link at its target name\n\n**Why**\n\nThese give more precise diagnostics for rare failure cases during atomic file writes, where a leftover or duplicated temp file could otherwise cause confusing or silent problems.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}