#log #pipe #stdout #stderr

io-mux

Provide multiple file descriptors writing into one in-order pipe, tagged by the source of data (e.g. stdout/stderr)

7 releases (stable)

1.4.0 Nov 15, 2020
1.3.0 Aug 22, 2020
1.1.0 Jul 27, 2020
1.0.1 Feb 7, 2020
0.1.1 Feb 5, 2020

#106 in Command-line interface

Download history 31/week @ 2020-08-10 26/week @ 2020-08-17 20/week @ 2020-08-24 20/week @ 2020-08-31 31/week @ 2020-09-07 10/week @ 2020-09-14 13/week @ 2020-09-21 26/week @ 2020-09-28 18/week @ 2020-10-05 11/week @ 2020-10-12 21/week @ 2020-10-19 23/week @ 2020-10-26 22/week @ 2020-11-02 33/week @ 2020-11-09 40/week @ 2020-11-16 24/week @ 2020-11-23

90 downloads per month
Used in 2 crates

MIT/Apache

21KB
265 lines

io-mux

A Mux provides a single receive end and multiple send ends. Data sent to any of the send ends comes out the receive end, in order, tagged by the sender.

Each send end works as a file descriptor. For instance, with io-mux you can collect stdout and stderr from a process, and highlight any error output from stderr, while preserving the relative order of data across both stdout and stderr.

Documentation

async

If you enable the async feature, io-mux additionally provides an AsyncMux type, which allows processing data asynchronously.

You may want to use this with async-process or async-pidfd to concurrently wait on the exit of a process and the muxed output and error of that process. Until the process exits, call AsyncMux::read() to get the next bit of output, awaiting that concurrently with the exit of the process. Once the process exits and will thus produce no further output, call AsyncMux::read_nonblock until it returns None to drain the remaining output out of the mux.

Portability

io-mux uses UNIX sockets, so it only runs on UNIX platforms. Support for non-Linux platforms is experimental, and has a major caveat in its semantics; please see the documentation for more details.

Dependencies

~330–640KB
~11K SLoC