[Bug 1878517] Re: please apply bash 5.0 patch 17

[Brian Murray]

** Changed in: bash (Ubuntu)
       Status: New => Triaged

** Changed in: bash (Ubuntu)
   Importance: Undecided => Medium

** Also affects: bash (Ubuntu Focal)
   Importance: Undecided
       Status: New

** Changed in: bash (Ubuntu Focal)
       Status: New => Triaged

** Changed in: bash (Ubuntu Focal)
   Importance: Undecided => Medium

** Tags removed: rls-ff-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1878517

Title:
  please apply bash 5.0 patch 17

Status in bash package in Ubuntu:
  Triaged
Status in bash source package in Focal:
  Triaged

Bug description:
  I am using Ubuntu 20.04 for development and has hit a bug in bash 5.0
  patch 16.

  I can't reproduce it in pure bash, but with bats from
  https://github.com/bats-core/bats-core/ it is very easy to repro:

  ```
  # cat << EOF > ya.bats
  check() {
  	echo "check $@"
  	ls -l /proc/self/fd
  }

  @test "here file" {
  	check -p <(echo "hey")
  	false
  }
  EOF

  $ bats ya.bats
  ```

  Normally the output should contain the line

     lr-x------ 1 kir kir 64 May 14 02:01 63 -> pipe:[4616918]

  which is a result of a "here file" created by bash via <(echo "hey").

  In my testing, about 50% of runs don't have /dev/fd/63 listed.

  I found out this is a manifest of a bug introduced in bash 5.0 patch
  16 (see http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-016)

  The bug is fixed in 5.0 patch 17 (see
  http://ftp.gnu.org/gnu/bash/bash-5.0-patches/bash50-017).

  Please update bash to patchlevel 17.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1878517/+subscriptions