Process Substitution Locks Shell

[leath-dub]

This is easily reproducible even on the master branch run the following

ls <(echo hello)

This should just print a temp path, however It ends up locking the shell - only responding to Ctrl-c.

[theclapp]

It's not completely broken. gosh appears to wait until something reads the FIFO it creates (whereas bash doesn't care). If you do that, it works:

$ cat <(echo .)
.

If you cat the FIFO in a different shell, that unblocks gosh:

<<<window 1>>>
$ ls -l <(echo .)
prw-r--r--@ 1 lmc  staff  0 Sep 16 11:35 /var/folders/9d/vt3kqx293xx8w3tn8m1jy_wc0000gn/T//sh-interp-12e05f50832eb231
<gosh blocks>

<<<window 2>>>
$ cat /var/folders/9d/vt3kqx293xx8w3tn8m1jy_wc0000gn/T//sh-interp-12e05f50832eb231
.
$

<<<window 1>>>
<gosh unblocks>
$

[mvdan]

I can reproduce this with test -e <(echo foo).

I misunderstood what man bash means when it says that process substitutions are run "asynchronously". I thought that meant that they ran concurrently but we still waited for them to finish, but it seems like bash does not, as is explained in https://unix.stackexchange.com/questions/388519/bash-wait-for-process-in-process-substitution-even-if-command-is-invalid.

I'm implementing that logic now.