Fix EPERM errors reading transient/locked files on Windows without Watchman #1007
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
As reported in #1001,
fs.lstat
operations on Windows can fail withEPERM
in certain circumstances - apparently when new files are either still being written or are about to be deleted.Currently, this bubbles up as a Watcher error, whereas it should be handled gracefully.
Reportedly the OS will follow up with another event on the file when it's ready to read, so we may safely ignore
EPERM
inadd
/change
event processing.NOTE: This raises the question of why we're watching build output/intermediate directories in the default React Native Metro config. We should almost certainly be ignoring them from Metro.
Differential Revision: D46803761