Need help on using piping to chain two powershell commands

[xiangkuan-peng]

Hello,
I am struggling with using piping to chain two powershell command.
I tried the following 2 ways to use piping but they both resulted in an error. However it works when I put the whole powershell command in the .WithArguments, am I understanding wrong about how to use piping to chain up two powershell commands?

First failed attempt:

StringBuilder sb = new StringBuilder();

var firstCmd = Cli.Wrap("powershell")
    .WithArguments("netsh interface portproxy show v4tov4");

var secondCmd = Cli.Wrap("powershell")
    .WithArguments("Select-String -Pattern '\\d+\\.\\d+\\.\\d+\\.\\d+\\s+\\d+\\s+\\d+\\.\\d+\\.\\d+\\.\\d+\\s+\\d+'")
    .WithStandardInputPipe(PipeSource.FromCommand(firstCmd))
    .WithStandardOutputPipe(PipeTarget.ToStringBuilder(sb));

var result = await secondCmd.ExecuteAsync(cancellationToken);
var a = sb.ToString();

Second failed attempt:

StringBuilder sb = new StringBuilder();

var firstCmd = Cli.Wrap("powershell")
    .WithArguments("netsh interface portproxy show v4tov4");

var secondCmd = Cli.Wrap("powershell")
    .WithArguments("Select-String -Pattern '\\d+\\.\\d+\\.\\d+\\.\\d+\\s+\\d+\\s+\\d+\\.\\d+\\.\\d+\\.\\d+\\s+\\d+'");

var cmd = firstCmd | secondCmd | PipeTarget.ToStringBuilder(sb);
var result = await cmd.ExecuteAsync(cancellationToken);
var a = sb.ToString();

Error:

System.AggregateException: One or more errors occurred. (Command execution failed because the underlying process (powershell.exe#26984) returned a non-zero exit code (1).

Command:
powershell Select-String -Pattern '\d+\.\d+\.\d+\.\d+\s+\d+\s+\d+\.\d+\.\d+\.\d+\s+\d+'

You can suppress this validation by calling `WithValidation(CommandResultValidation.None)` on the command.)
 ---> CliWrap.Exceptions.CommandExecutionException: Command execution failed because the underlying process (powershell.exe#26984) returned a non-zero exit code (1).

Command:
powershell Select-String -Pattern '\d+\.\d+\.\d+\.\d+\s+\d+\s+\d+\.\d+\.\d+\.\d+\s+\d+'

You can suppress this validation by calling `WithValidation(CommandResultValidation.None)` on the command.
   at CliWrap.Command.ExecuteAsync(ProcessEx process, CancellationToken forcefulCancellationToken, CancellationToken gracefulCancellationToken) in /_/CliWrap/Command.Execution.cs:line 271
   at CliWrap.Command.ExecuteAsync(ProcessEx process, CancellationToken forcefulCancellationToken, CancellationToken gracefulCancellationToken) in /_/CliWrap/Command.Execution.cs:line 287
   at CliWrap.Command.ExecuteAsync(ProcessEx process, CancellationToken forcefulCancellationToken, CancellationToken gracefulCancellationToken) in /_/CliWrap/Command.Execution.cs:line 287
   at CliWrap.Command.ExecuteAsync(ProcessEx process, CancellationToken forcefulCancellationToken, CancellationToken gracefulCancellationToken) in /_/CliWrap/Command.Execution.cs:line 287

The working alternative:

var firstCmd = Cli.Wrap("powershell")
    .WithArguments("netsh interface portproxy show v4tov4 | Select-String -Pattern '\\d+\\.\\d+\\.\\d+\\.\\d+\\s+\\d+\\s+\\d+\\.\\d+\\.\\d+\\.\\d+\\s+\\d+'")
    .WithStandardOutputPipe(PipeTarget.ToStringBuilder(sb));
var result = await firstCmd.ExecuteAsync(cancellationToken);

[Tyrrrz]

If you run the command via ExecuteBufferedAsync(), you will get more info in the exception message

[xiangkuan-peng]

@Tyrrrz
After changing to ExecuteBufferedAsync() I see that the it is complaining the second command received empty array.

The error details:

System.AggregateException: One or more errors occurred. (Command execution failed, see the inner exception for details.

Standard error:
Select-String : Cannot bind argument to parameter 'Path' because it is an empty array.
At line:1 char:1
+ Select-String -Pattern '\d+\.\d+\.\d+\.\d+\s+\d+\s+\d+\.\d+\.\d+\.\d+ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Select-String], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyArrayNotAllowed,Microsoft.PowerShell.Commands.Selec
   tStringCommand)
 ---> CliWrap.Exceptions.CommandExecutionException: Command execution failed, see the inner exception for details.

Standard error:
Select-String : Cannot bind argument to parameter 'Path' because it is an empty array.
At line:1 char:1
+ Select-String -Pattern '\d+\.\d+\.\d+\.\d+\s+\d+\s+\d+\.\d+\.\d+\.\d+ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (:) [Select-String], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationErrorEmptyArrayNotAllowed,Microsoft.PowerShell.Commands.Selec
   tStringCommand
 ---> CliWrap.Exceptions.CommandExecutionException: Command execution failed because the underlying process (powershell.exe#11760) returned a non-zero exit code (1).

Command:
powershell Select-String -Pattern '\d+\.\d+\.\d+\.\d+\s+\d+\s+\d+\.\d+\.\d+\.\d+\s+\d+'

You can suppress this validation by calling `WithValidation(CommandResultValidation.None)` on the command.
   at CliWrap.Command.ExecuteAsync(ProcessEx process, CancellationToken forcefulCancellationToken, CancellationToken gracefulCancellationToken) in /_/CliWrap/Command.Execution.cs:line 271
   at CliWrap.Command.ExecuteAsync(ProcessEx process, CancellationToken forcefulCancellationToken, CancellationToken gracefulCancellationToken) in /_/CliWrap/Command.Execution.cs:line 287
   at CliWrap.Command.ExecuteAsync(ProcessEx process, CancellationToken forcefulCancellationToken, CancellationToken gracefulCancellationToken) in /_/CliWrap/Command.Execution.cs:line 287
   at CliWrap.Command.ExecuteAsync(ProcessEx process, CancellationToken forcefulCancellationToken, CancellationToken gracefulCancellationToken) in /_/CliWrap/Command.Execution.cs:line 287
   at CliWrap.Buffered.BufferedCommandExtensions.<>c__DisplayClass0_0.<<ExecuteBufferedAsync>b__0>d.MoveNext() in /_/CliWrap/Buffered/BufferedCommandExtensions.cs:line 53
   --- End of inner exception stack trace ---
   at CliWrap.Buffered.BufferedCommandExtensions.<>c__DisplayClass0_0.<<ExecuteBufferedAsync>b__0>d.MoveNext() in /_/CliWrap/Buffered/BufferedCommandExtensions.cs:line 65

Can this be a bug for piping powershell commands?

[Tyrrrz]

Try piping instead into echo or something else that prints back the stdin, to debug and isolate the problem