interprocess
interprocess copied to clipboard
kotauskas
Multifunctional cross-platform interprocess communication toolkit for Rust.
**Describe the bug** First off thanks for this package it is a nice abstraction for socket-like behavior. I use this in a project of mine aimed at providing OS agnostic...
i was trying to build this crate from `main` to see if recent changes would fix an issue i was having, but instead i started getting this error: ``` error:...
**Describe the bug** Whenever I build with `interprocess` (1.2.1) as a dependency without even using the dependency anywhere in the code, I get the following error: ``` Compiling tokio v1.36.0...
``` error: test failed, to rerun pass `--test tokio_named_pipe` Caused by: process didn't exit successfully: `\interprocess\target\debug\deps\tokio_named_pipe.exe` (exit code: 0xc0000374, STATUS_HEAP_CORRUPTION) ``` ``` Caused by: process didn't exit successfully: `\interprocess\target\debug\deps\tokio_named_pipe.exe` (exit...
**Describe the bug** LocalSocketListener.accept() should return `WouldBlock`, but it returns `Uncategorized` in Windows. **To Reproduce** ```rust match LocalSocketListener::bind("@name") { Ok(listener) =>{ let _ = listener.set_nonblocking(true); loop { match listener.accept() {...
We want to use interprocess in https://github.com/n0-computer/quic-rpc for use in https://github.com/n0-computer/iroh . We are seeing several test failures with the currently published version, specifically on windows. They **all** seem to...
**Describe the bug** cant write to a socket quickly on Windows this works completely fine on Unix but causes a block forever on Windows **To Reproduce** Write to the socket...
AF_UNIX has been available on Windows since 2017 (https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/). Can we use Unix sockets instead of named pipes on Windows?
**Describe the bug** When I run the tests they succeeds at first, but running them again a second time right after the first and the local_socket_stream test fails for me....
**Describe the bug** Once a socket has been opened on one version of PowerShell, other versions of PowerShell cannot send/read messages to/from the opened socket. **To Reproduce** Using `LocalSocketStream::connect("@known-name.sock")`: 1)...