9.0.0 release about simple-exec HOT 5 CLOSED

I believe CliWrap may have what you need as part of its piping API

That's correct.

from simple-exec.

@dazinator stdin, stdout, and stderr are intentionally only exposed as strings as part of SimpleExec's deliberate simplicity. At one time I considered exposing streams etc. but I believe it's beyond the scope of SimpleExec and, not least, it's not something I need. You may want to take a look at a more advanced library for your needs. For example, I believe CliWrap may have what you need as part of its piping API. /cc @Tyrrrz

from simple-exec.

I've just come accross this library and jumped straight in using version 9 alpha 1 on windows 10 and ubuntu 20.04 - it is working well, and enabled me to remove some flakier process handling. Thank you for your hard work on this.

from simple-exec.

@dazinator that's great to hear. Hopefully I'll be able to move 9.0.0 towards RTM soon. Any feedback you may have is welcome.

from simple-exec.

I do have a question,

I am trying to execute docker config create foo and supply some data through stdin as described here: https://docs.docker.com/engine/reference/commandline/config_create/

The data I need to supply through stdin corresponds to some file content held as byte[] in the database.

The issue I have is that I can only supply the data for the stdin as a string argument via SimpleExec. This means I have to convert from the raw byte[] to a string first. This has me wondering if I could hit issues with encoding. I will do some tests, however it would be good if the stdin could be written as raw bytes!

from simple-exec.