Support for Scala Native. There seem to be a few bugs:
Scala Native bugs:
start() of a ProcessBuilder do not throw exceptions. It seems to create an "empty" process. We can't do anything about this because it is impossible to differentiate a malformed empty process from a real process that seems empty.
A script get executed only when using bash. There is a workaround for this.
Scala Native or ZIO bug
Sometimes, when using ZStreams as standard input, it's impossible to read from the standard output of a process. It's fine when using a Java InputStream instead. I don't know if it is the Process that blocks standard output or if it's the ZStream that is not sending anything. After closing the standard input, nothing has been sent. It doesn't work either when a ZStream is transformed into an InputStream. I don't know the cause of this bug.
So, as long as non-existent commands are not executed and an InputStream is used instead of ZStreams when there are problems, the rest is completely functional.
The first two bugs should be easy to solve within Scala Native.
Support for Scala Native. There seem to be a few bugs:
Scala Native bugs:
start()
of aProcessBuilder
do not throw exceptions. It seems to create an "empty" process. We can't do anything about this because it is impossible to differentiate a malformed empty process from a real process that seems empty.bash
. There is a workaround for this.Scala Native or ZIO bug Sometimes, when using ZStreams as standard input, it's impossible to read from the standard output of a process. It's fine when using a Java
InputStream
instead. I don't know if it is theProcess
that blocks standard output or if it's theZStream
that is not sending anything. After closing the standard input, nothing has been sent. It doesn't work either when a ZStream is transformed into an InputStream. I don't know the cause of this bug.So, as long as non-existent commands are not executed and an
InputStream
is used instead ofZStreams
when there are problems, the rest is completely functional. The first two bugs should be easy to solve within Scala Native./claim #4