EPERM error on Windows when multiple processes try to write the same file

Open
  • Is something wrong?
#28 6 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #29 by @mekwall — closed without merging

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
operating-systems, tooling

Research direction

Start with the write-file-atomic behavior described in the issue and run the linked write-atomic-issue reproduction on Windows. Compare the existing handling referenced in #22 with concurrent sync and async writes from multiple processes; done means the reproduction no longer raises EPERM during concurrent writes or renames.

Written by the indexing model from the issue text.

Description

When write-file-atomic is used by multiple processes (e.g. in worker-farm) it can run into a race condition where the same file is being written/renamed concurrently. On Windows it causes the following error:

Error: EPERM: operation not permitted, rename '...' -> '...'

#22 seems to address this issue for async writes within the same process, but the issue still exists for parallel sync/async writes.

Here's a repro that demonstrates the problem: https://github.com/asapach/write-atomic-issue

Original issue: facebook/jest#4444

Dominant language
JavaScript
Stars
256
Forks
51
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from npm/write-file-atomic

All issues in npm/write-file-atomic

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.