fix(export): harden post-merge file handling#444
Conversation
|
ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe PR widens rename-failure handling by treating ChangesExport Robustness
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
20f111e to
81bfd2d
Compare
Description
Follow-up to #410 for two final CodeRabbit export hardening comments that were left after the merge.
Changes Made
EEXISTfrom the firstfs.rename(tempPath, destinationPath)as recoverable so the safe copy/replace fallback can run on Windows overwrite cases.isAllowedLocalReadPath()beforerealpath/statfor non-media local read paths, then keep the realpath re-check for symlink protection.EEXISTfallback path.Validation
npm test -- electron/ipc/register/export.test.ts electron/ipc/export/native-video.test.ts(67tests)npx biome check --formatter-enabled=false electron/ipc/register/export.ts electron/ipc/register/export.test.tsnpx tsc --noEmitgit diff --checkNotes
This does not change CUDA/D3D11 routing, browser mic behavior, or exporter feature gates from #410.
Summary by CodeRabbit
Bug Fixes
Tests