-
**Why?**
Currently, `Deno.connect` only supports IPC for unix (using unstable `transport: "unix"`). There should be named pipes support too, which would allow IPC on Windows (as NodeJS' `net` mode …
-
Hi there :-)
I hope I'm reporting this to the right place, let me know if this isn't it.
I noticed there is support for UNIX sockets in asyncio, but there is no documented support for named pipes on…
-
we are experiencing issues with IPC sockets reliability on Windows. related issues #1175 and #1567
on macOS it works much more reliably. One of the differences between the two systems is that Windows…
-
**Please describe the problem.**
At the moment it looks like that termdebug for Windows use only the `prompt` alternative. However, newer Windows version include conpty that could enable the utili…
-
### Issue Description
Hello folks, When I tried to build the Store (MSIX) version of [Telegram Desktop](https://github.com/telegramdesktop/tdesktop) application in VS 2022, my build failed with the…
-
go-spiffe now supports Named Pipes in gRPC target strings, since v2.1.1.
This can simplify the current usage of named pipes in SPIRE through the go-spiffe library.
-
I am using Doppler to handle secrets and I am running `doppler run --mount .env --command "while true; do sleep 1; done"` which creates `.env` as a named pipe. `dotenvy` fails to parse anything from t…
-
```
Hi Jarl,
does this RCF1.0 supports named pipes in both Windows and Unix Flavours ?
--Raveendra
```
Original issue reported on code.google.com by `mraveend...@gmail.com` on 7 May 2009 at 9:27
-
> ```
> Prisma schema loaded from prisma\schema.prisma
> Datasource "db": MySQL database "prismadb" at "localhost:3306"
>
> Error: Migration engine error:
> Error querying the database: Named pi…
-
1. What version of Go are you using (`go version`)?
go version go1.7rc3 windows/amd64
2. What operating system and processor architecture are you using (`go env`)?
set GOARCH=amd64
set GOBIN=…