Panic in windows cmd.exe with piped input

[teamunicycle]

Please tick this box to confirm you have reviewed the above.

• I have a different issue.

What version of ripgrep are you using?

ripgrep 15.1.0

How did you install ripgrep?

cargo install

What operating system are you using ripgrep on?

windows 11, 25H2

Describe your bug.

ripgrep panics

What are the steps to reproduce the behavior?

Windows 11, cmd.exe. Doesn't happen in powershell.

piped help from eza command into rg with no parameters:

eza --help | rg

Works fine if there's actually an expression after rg, which is of course what I meant to do
eza --help | rg git
Works fine with other programs writing to stdout.

What is the actual behavior?

eza --help | rg --debug
rg: DEBUG|rg::flags::parse|C:\Users\Me.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\ripgrep-15.1.0\crates\core\flags\parse.rs:97: no extra arguments found from configuration file
rg: DEBUG|rg::flags::hiargs|C:\Users\Me.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\ripgrep-15.1.0\crates\core\flags\hiargs.rs:954: read CWD from environment: C:\Users\Me
rg: ripgrep requires at least one pattern to execute a search

thread 'main' (80452) panicked at /rustc/e408947bfd200af42db322daf0fadfe7e26d3bd1/library\std\src\io\stdio.rs:1165:9:
failed printing to stdout: The pipe is being closed. (os error 232)
stack backtrace:
0: 0x7ff6c43db900 -
1: 0x7ff6c43b21b1 -
2: 0x7ff6c43dac74 -
3: 0x7ff6c43da895 -
4: 0x7ff6c43e1775 -
5: 0x7ff6c43e171f -
6: 0x7ff6c43e170e -
7: 0x7ff6c44cf8ed - git_trace_set
8: 0x7ff6c435bf94 -
9: 0x7ff6c4382796 -
10: 0x7ff6c43ae325 -
11: 0x7ff6c44cc29c - git_trace_set
12: 0x7ff8afb1e8d7 - BaseThreadInitThunk
13: 0x7ff8b098c48c - RtlUserThreadStart

What is the expected behavior?

Should have just told me to include a pattern in the command

[ltrzesniewski]

I could reproduce this, but it seems like an issue in eza:

• other commands like bat --help | rg don't exhibit this behavior.
• piping eza --help to something else which fails, such as eza --help | bat --lol shows the same panic:

   error: unexpected argument '--lol' found
   
     tip: to pass '--lol' as a value, use '-- --lol'
   
   Usage: bat [OPTIONS] [FILE]...
          bat <COMMAND>
   
   thread 'main' (22288) panicked at /rustc/59807616e1fa2540724bfbac14d7976d7e4a3860/library\std\src\io\stdio.rs:1165:9:
   failed printing to stdout: The pipe is being closed. (os error 232)
   note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace