why3 issueshttps://gitlab.inria.fr/why3/why3/-/issues2020-03-03T01:52:26+01:00https://gitlab.inria.fr/why3/why3/-/issues/448Named pipes on recent Windows versions2020-03-03T01:52:26+01:00Ghost UserNamed pipes on recent Windows versionsWe are having some issues when running Why3 on Cygwin+MinGW, namely due to the usage of named pipes in `src/driver/prove_client.ml`, function `client_connect`.
```
client_connect: connection failed: No such file or directory (open,\\.\p...We are having some issues when running Why3 on Cygwin+MinGW, namely due to the usage of named pipes in `src/driver/prove_client.ml`, function `client_connect`.
```
client_connect: connection failed: No such file or directory (open,\\.\pipe\C:\OCaml64\tmp\why3server1a9f15sock) (socket_name=C:\OCaml64\tmp\why3server1a9f15sock)
```
I've never used named pipes on Windows so I'm not familiar with them. I did find [this SO question](https://stackoverflow.com/questions/46497926/named-pipes-no-longer-a-thing-in-windows-10-version-1709) mentioning possible changes in recent Windows (I am using 1903, which is more recent than the 1709 version mentioned in the question), so while I try to dig deeper, could you please tell me if Why3 is being tested on recent Windows versions?1.3.0