Jonathan Marler 32f602ad16
std.os.windows: handle OBJECT_NAME_INVALID in OpenFile (#19288)
It's been seen on Windows 11 (22H2) Build 22621.3155 that NtCreateFile
will return the OBJECT_NAME_INVALID error code with certain path names.
The path name we saw this with started with `C:Users` (rather than
`C:\Users`) and also contained a `$` character.  This PR updates our
OpenFile wrapper to propagate this error code as `error.BadPathName`
instead of making it `unreachable`.

see https://github.com/marler8997/zigup/issues/114#issuecomment-1994420791
2024-03-13 21:39:20 -04:00
..
2024-02-23 02:37:11 -07:00
2024-03-11 12:25:03 +01:00
2023-11-22 13:24:27 -05:00
2024-03-10 18:13:30 -07:00
2024-03-10 18:13:30 -07:00
2024-03-10 18:13:30 -07:00
2024-03-10 18:13:30 -07:00
2024-03-10 18:13:30 -07:00
2024-02-05 11:55:14 +03:30
2024-03-01 17:42:54 -08:00
2023-10-25 04:28:30 -04:00
2024-02-09 14:02:57 -08:00
2024-01-24 12:48:12 +01:00
2024-03-13 18:35:07 -07:00
2024-03-10 18:13:30 -07:00
2024-02-01 15:22:36 +02:00
2024-02-08 15:39:28 +01:00
2024-03-10 18:13:30 -07:00
2024-03-10 18:13:30 -07:00
2024-03-11 12:25:51 +01:00
2024-02-25 11:22:10 +01:00
2024-02-26 20:11:43 -08:00
2023-10-21 21:24:55 +00:00