You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
13.0.0
(for reference, 12.1.1 does not have this issue)
How did you install ripgrep?
Downloaded the binary from GitHub release. Installed via dpkg -i
What operating system are you using ripgrep on?
WSL2 5.10.60.1-microsoft-standard-WSL2 #1 SMP Wed Aug 25 23:20:18 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
POP!_OS 5.13.0-7620-generic #20~1634827117~21.04~874b071-Ubuntu SMP Fri Oct 29 15:06:55 UTC x86_64 x86_64 x86_64 GNU/Linux
Describe your bug.
Node.js child_process.exec api allow you to spawn a shell and execute a command. In 12.1.1, rg works as expected. In 13.0.0, the exec never finishes, i.e. the callback is never invoked.
What are the steps to reproduce the behavior?
(the repro uses execSync instead of exec, in order to collect error log. exec has no observable output)
ripgrep will automatically detect if stdin exists and search stdin for a regex pattern, e.g. ls | rg foo. In some environments, stdin may exist when it shouldn’t. To turn off stdin detection explicitly specify the directory to search, e.g. rg foo ./.
This is likely relevant to you. There are likely also parameters you can pass to Node's "create process" API that will close off stdin and not make it look readable.
What version of ripgrep are you using?
13.0.0
(for reference, 12.1.1 does not have this issue)
How did you install ripgrep?
Downloaded the binary from GitHub release. Installed via
dpkg -i
What operating system are you using ripgrep on?
WSL2
5.10.60.1-microsoft-standard-WSL2 #1 SMP Wed Aug 25 23:20:18 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
POP!_OS
5.13.0-7620-generic #20~1634827117~21.04~874b071-Ubuntu SMP Fri Oct 29 15:06:55 UTC x86_64 x86_64 x86_64 GNU/Linux
Describe your bug.
Node.js child_process.exec api allow you to spawn a shell and execute a command. In 12.1.1, rg works as expected. In 13.0.0, the exec never finishes, i.e. the callback is never invoked.
What are the steps to reproduce the behavior?
(the repro uses execSync instead of exec, in order to collect error log. exec has no observable output)
index.js
node index.js
For comparison. running the command
rg const --trace
in terminal (also 13.0.0)In terminal,
echo $?
return0
Running
node index.js
with rg 12.1.1Running
rg const --trace
in terminal with rg 12.1.1What do you think ripgrep should have done?
Possible a regression introduced by version 13? I'm not a rust expert so no clue on what might have caused it. Some wild guesses:
The text was updated successfully, but these errors were encountered: