On Windows you get fewer spurious file-watch errors when a file is briefly locked.
What's wrong with this entry?
File watchers now handle an EPERM error on Windows by trying to open the file for reading before reporting a failure, which stops spurious watch errors on files Windows briefly locks.
l.close.bind(l)
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Windows policy helpers can be PowerShell scripts
Both mention window
-
v2.1.234
Windows sandbox refusals now say why an exclusion did not apply
Both mention window
-
v2.1.234
Terminal is restored on Ctrl+Break on Windows
Both mention window