Alternative to ports for running external programs. It provides back-pressure, non-blocking io, and solves port related issues
APACHE-2.0 License
Full Changelog: https://github.com/akash-akya/exile/compare/v0.9.1...v0.10.0
Published by akash-akya 9 months ago
Full Changelog: https://github.com/akash-akya/exile/compare/v0.8.0...v0.9.1
Published by akash-akya 10 months ago
Full Changelog: https://github.com/akash-akya/exile/compare/v0.7.0...v0.8.0
Published by akash-akya about 1 year ago
:enable_stderr
is removed in favor of :stderr
.enable_stderr
option, please switch to stderr
as mentioned below
enable_stderr: true
=> stderr: :consume
enable_stderr: false
=> stderr: :console
Full Changelog: https://github.com/akash-akya/exile/compare/v0.6.0...v0.7.0
Published by akash-akya over 1 year ago
The error type raised by the Exile.stream!/2
is changed.
Previously, it used to raise Exile.Process.Error
error when program exits with non-zero exit status and epipe.
Now Exile.Stream.AbnormalExit
will be raised with exit_status
field in the error set. Now caller can
catch the error and fetch exit status.
stream!/1
opts by @balins in https://github.com/akash-akya/exile/pull/25
Full Changelog: https://github.com/akash-akya/exile/compare/v0.5.0...v0.6.0
Published by akash-akya over 1 year ago
Full Changelog: https://github.com/akash-akya/exile/compare/v0.4.0...v0.5.0
Published by akash-akya over 1 year ago
Full Changelog: https://github.com/akash-akya/exile/compare/v0.3.0...v0.4.0
Published by akash-akya over 1 year ago
Full Changelog: https://github.com/akash-akya/exile/compare/v0.2.0...v0.3.0
Published by akash-akya over 1 year ago
This is mostly complete rewrite with the focus on how the process
gen-server state-machine behave when reader and writer run
concurrently. While it already supported that previously, but the API
surface was large (such as support for concurrent await_exit, multiple
writer etc.). And there were some corner cases such as handling of
EPIPE
. With the new rewrite, the Process server now offloads the
pooling and concurrent read/write to user.
This is a breaking change for Exile.Process
. It was already
mentioned as unstable and user should always use Exile.stream!
.
Users using Exile.stream!
should be unaffected by the change, unless
they depend on few corner cases when command exit abnormally.
Full Changelog: https://github.com/akash-akya/exile/compare/v0.1.0...v0.2.0
Published by akash-akya almost 2 years ago
First release