« Changelog History


CliWrap v3.4.1 Release Notes

    • 🛠 Fixed an issue where calling Cli.Wrap("non-existing-target").ExecuteAsync() on a target that doesn't exist resulted in an invalid CommandTask, due to the fact that the associated exception was thrown in an asynchronous context that was not observed prior to that point. This had a few consequences, such as the fact that the returned CommandTask had invalid ProcessId of 0. It also caused event stream execution models (Observe() and ListenAsync()) to incorrectly yield StartedCommandEvent even if the process was not able to actually start.