earonesty

wsl2 is just linux, not a windows runner. not really helpful for ci/cd of windows tools, services or packages. native windows support would rock for devs who are coding up...

no idea why this is closed. installation on windows is definitely not supported. wsl2 is not helpful at all for unit testing or ci/cd of tools that are designed to...

our use case: - we are perfectly fine with letting winfsp handle locking - all we really need is the contents of the FILE_SHARE_XXXX flags that *were* passed in on...

imagine a simple pass through fs. if the user mode file is backed by a file that is located on a network share, we need to open the networked file...

Sweet thanks! Hopefully other people find this thread useful. Literally fixed everything (already tested it - works fine), and we get to rip out all the hacks.

Yes, this problem also occurs with the C, layer, with the same STATUS_INVALID_OWNER issue. On win10, tested just now, running as an admin user. Very easy to reproduce as long...

procmon logs: - failure even with the 512 byte sector size: https://pastebin.com/g2qa1PV3 - success with NTFS: https://pastebin.com/KCVwarx7 - success with AIRFS: https://pastebin.com/Usxrbnch (partial log, excluded the get retrieval spam, stops...

Yeah, that sounds like a great solution. In the procmon logs, I see one STATUS_SUCCESS followed by one STATUS_END_OF_FILE for the NTFS hits. I'd bet that simply STATUS_END_OF_FILE would be...

Yes, I will test it. I'm not sure I've built winfsp from scratch before, tho. On Fri, Oct 23, 2020 at 4:05 PM Bill Zissimopoulos wrote: > If I make...

Note: In order to conform to the documentation on socket timeouts they must get reset each time a read is made. So there's no reason for a "very complex" solution.,...