Skip to content

Releases: akash-akya/exile

v0.11.0

08 Jul 16:51
Compare
Choose a tag to compare

What's Changed

  • tests: allow stderr/sigterm tests to work across platforms by @dch in #44
  • Switch to nix based github action for macos in #45
  • Add support for redirecting stderr to stdout in #46. Thanks to @dch for helping with docs

New Contributors

  • @dch made their first contribution in #44

Full Changelog: v0.10.0...v0.11.0

v0.10.0

27 May 16:55
Compare
Choose a tag to compare

What's Changed

New Contributors

  • @feld made their first contribution in #40

Full Changelog: v0.9.1...v0.10.0

v0.9.1

24 Jan 19:31
Compare
Choose a tag to compare

What's Changed

  • Makefile: Fix for {Net,Free,Open}BSD and generic $CFLAGS in environ by @lanodan in #36
  • Ignore additional output in the stdout while asserting in #38

New Contributors

Full Changelog: v0.8.0...v0.9.1

v0.8.0

15 Dec 19:07
Compare
Choose a tag to compare

What's Changed

  • Fix stderr FD leak in #33

Full Changelog: v0.7.0...v0.8.0

v0.7.0

27 Jul 17:46
Compare
Choose a tag to compare

Breaking Changes

  • Support suppressing stderr output in #30
    Exile now supports suppressing stderr outputs completely.
    To unify all stderr redirection options :enable_stderr is removed in favor of :stderr.
    If you were using enable_stderr option, please switch to stderr as mentioned below
    • enable_stderr: true => stderr: :consume
    • enable_stderr: false => stderr: :console
      For more details check the documentation

What's Changed

  • Remove UB sanitizer in #29 and #32

Full Changelog: v0.6.0...v0.7.0

v0.6.0

27 Jun 18:34
Compare
Choose a tag to compare

Breaking Changes

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.

What's Changed

  • Add option to stream exit_status in #26
  • Add separate exception for non-zero process exit in #26
  • Fix missing typespecs for stream!/1 opts by @balins in #25

New Contributors

Full Changelog: v0.5.0...v0.6.0

v0.5.0

22 May 19:03
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.4.0...v0.5.0

v0.4.0

02 May 18:19
Compare
Choose a tag to compare

What's Changed

  • Start process within Enumerable reduce in #21
  • Flush process down message if process exit successfully in #21

Full Changelog: v0.3.0...v0.4.0

v0.3.0

29 Apr 14:07
Compare
Choose a tag to compare

What's Changed

  • Fix spawner not being found when under a release by @g-andrade in #19

New Contributors

Full Changelog: v0.2.0...v0.3.0

v0.2.0

19 Apr 11:04
Compare
Choose a tag to compare

Breaking Changes

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.

Non Breaking Changes

New Contributors

Full Changelog: v0.1.0...v0.2.0