TanninOne

Saw ERROR_NOT_READY (code 21) happen on a call to fsync - mapped to UNKNOWN. According to MS this usually indicates a serious hardware error, not sure what it should be...

Another "UNKNOWN" one: ERROR_VIRUS_INFECTED (code 225) happens when writing a file. Not sure how to map that...

ERROR_DEVICE_HARDWARE_ERROR (483) reported on CreateFile. Windows reports it as "The request failed due to a fatal device hardware error." This followed immediately after a ERROR_IO_DEVICE which is actually already mapped...

I kind of wish there a libuv code that was a bit more precise for the "ERROR_VIRUS_INFECTED" case because in that case the user actually may have to take action...

Develop software for Windows for a bit and you will learn why it doesn't work like that. Some AVs will silently delete/quarantine files without ever reporting it. Many users will...

If introducing a new error code in libuv is no option, maybe mapping ERROR_VIRUS_INFECTED to EPERM is more appropriate than EIO.

Yes, but one could argue that the virus scanner here acts like a form of file protection, does it really matter how and for what purpose the file is "protected"?...

> we have some (easily fixable) gaps in our Windows error mapping I don't really fully agree with "some" or "easily fixable" here. There are at least 40 error messages...

> In the immortal words of The Dude: that's just, like, your opinion, man. Nor did I claim it was. You said "I don'think anyone disagrees with the first one"...

> Abstracting things means we'll walways lose something on each platform in the process So then, can you quote a few examples what functionalities a linux system "loses" (like ACLs...