ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "jeremyevans0 (Jeremy Evans)" <noreply@ruby-lang.org>
To: ruby-core@neon.ruby-lang.org
Subject: [ruby-core:110822] [Ruby master Bug#19130] MRI failing when executing shell builtin commands with Errno::ENOENT
Date: Sat, 19 Nov 2022 23:07:54 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-100179.20221119230753.52558@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-19130.20221114020014.52558@ruby-lang.org

Issue #19130 has been updated by jeremyevans0 (Jeremy Evans).


I don't think this is a bug.  Ruby's behavior for the Kernel backtick method (what `%x` uses) is that a shell is only used if Ruby thinks it is necessary.  If Ruby doesn't determine the use of a shell is necessary, it will directly execute the program instead of using a shell.  Here's an example showing the behavior:

```
# Simple command line that Ruby doesn't use a shell for
$ ruby -e 'puts %x{ps al}.split("\n").grep(/#{$$}/)'
 1000 54241 42309   3   2   0 61228 15220 kqread  S+     pi    0:00.14 ruby -e puts %x{ps al}.split("\\n").grep(/#{$$}/) (ruby31)
 1000 24047 54241   3  31   0   736   756 -       R+pU/0 pi    0:00.00 ps -al

# Command line including pipe, which Ruby does use a shell for
$ ruby -e 'puts %x{ps al | grep #{$$}}'
 1000 37783 42309   3   2   0 61228 15224 kqread  S+     pi    0:00.14 ruby -e puts %x{ps al | grep #{$$}} (ruby31)
 1000 95607 37783   3  18   0   872   880 sigsusp S+p    pi    0:00.01 sh -c ps al | grep 37783
 1000 47178 95607   3  31   0   172   460 -       R+/2   pi    0:00.00 grep 37783
```

If you want to force the use of a shell when would not be used, you need to manually execute the shell:

```ruby
%x{sh -c "type type"}
# => "type is a shell builtin\n"
```

----------------------------------------
Bug #19130: MRI failing when executing shell builtin commands with Errno::ENOENT
https://bugs.ruby-lang.org/issues/19130#change-100179

* Author: ifiht (Mikal R)
* Status: Open
* Priority: Normal
* ruby -v: 3.2.0
* Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
Sorry if this came up already, Google & Redmine came up blank but maybe I missed it. Bug was found on 3.0.0 but I tested on 3.2.0-preview1 and it's present on both.

Trying to execute any shell builtin commands from irb or script fails with `No such file or directory - <cmd> (Errno::ENOENT)`

```
└$ rvm list
 * ruby-3.0.0 [ x86_64 ]
=> ruby-3.2.0-preview1 [ x86_64 ]
```
MRI 3.0.0:
```
3.0.0 :001 > %x(type ls)
Traceback (most recent call last):
        5: from /home/ifiht/.rvm/rubies/ruby-3.0.0/bin/irb:23:in `<main>'
        4: from /home/ifiht/.rvm/rubies/ruby-3.0.0/bin/irb:23:in `load'
        3: from /home/ifiht/.rvm/rubies/ruby-3.0.0/lib/ruby/gems/3.0.0/gems/irb-1.3.0/exe/irb:11:in `<top (required)>'
        2: from (irb):1:in `<main>'
        1: from (irb):1:in ``'
Errno::ENOENT (No such file or directory - type)
3.0.0 :002 > %x(cd /home/ifiht)
Traceback (most recent call last):
        6: from /home/ifiht/.rvm/rubies/ruby-3.0.0/bin/irb:23:in `<main>'
        5: from /home/ifiht/.rvm/rubies/ruby-3.0.0/bin/irb:23:in `load'
        4: from /home/ifiht/.rvm/rubies/ruby-3.0.0/lib/ruby/gems/3.0.0/gems/irb-1.3.0/exe/irb:11:in `<top (required)>'
        3: from (irb):1:in `<main>'
        2: from (irb):2:in `rescue in <main>'
        1: from (irb):2:in ``'
Errno::ENOENT (No such file or directory - cd)
3.0.0 :003 > exit
```
MRI 3.2.0:
```
:001 > %x(type ls)
(irb):1:in ``': No such file or directory - type (Errno::ENOENT)
        from (irb):1:in `<main>'
        from /home/ifiht/.rvm/rubies/ruby-3.2.0-preview1/lib/ruby/gems/3.2.0+1/gems/irb-1.4.1/exe/irb:11:in `<top (required)>'
        from /home/ifiht/.rvm/rubies/ruby-3.2.0-preview1/bin/irb:25:in `load'
        from /home/ifiht/.rvm/rubies/ruby-3.2.0-preview1/bin/irb:25:in `<main>'
 :002 > `type ls`
(irb):2:in ``': No such file or directory - type (Errno::ENOENT)
        from (irb):2:in `<main>'
        from /home/ifiht/.rvm/rubies/ruby-3.2.0-preview1/lib/ruby/gems/3.2.0+1/gems/irb-1.4.1/exe/irb:11:in `<top (required)>'
        from /home/ifiht/.rvm/rubies/ruby-3.2.0-preview1/bin/irb:25:in `load'
        from /home/ifiht/.rvm/rubies/ruby-3.2.0-preview1/bin/irb:25:in `<main>'
```

Assuming this is a bug? Let me know if shell builtins are deliberately excluded for some reason, I'll try to work around it.



-- 
https://bugs.ruby-lang.org/

  parent reply	other threads:[~2022-11-19 23:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14  2:00 [ruby-core:110737] [Ruby master Bug#19130] MRI failing when executing shell builtins with Errno::ENOENT ifiht (Mikal R)
2022-11-18  9:50 ` [ruby-core:110808] [Ruby master Bug#19130] MRI failing when executing shell builtin commands " mjrzasa
2022-11-18  9:50 ` [ruby-core:110809] " mjrzasa
2022-11-18  9:53 ` [ruby-core:110810] " mjrzasa
2022-11-19 22:45 ` [ruby-core:110821] " ifiht (Mikal R)
2022-11-19 23:07 ` jeremyevans0 (Jeremy Evans) [this message]
2022-11-21 15:24 ` [ruby-core:110839] " nobu (Nobuyoshi Nakada)
2022-11-21 15:31 ` [ruby-core:110840] " nobu (Nobuyoshi Nakada)
2022-11-24 23:34 ` [ruby-core:110884] " jeremyevans0 (Jeremy Evans)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-100179.20221119230753.52558@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    --cc=ruby-core@neon.ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).