Immediate Failure event-pipe error

[sscotth]

I haven't been able to narrow when or how I get this error:

But it usually occurs when I run quite a large script over and over again. Restarting the computer usually fixes this, but not always.

Once my system gets in this "state", I can't even run the demo.sh file in this repo.

On this system, the current $TMPDIR is /var/folders/6b/mm5f4rz116lbp_9rphrmv4s00000gn/T/

This line of code:

bash-concurrent/concurrent.lib.sh

Line 1078 in fc265c7

__crt__status_dir=$(mktemp -d "${TMPDIR:-/tmp}/concurrent.lib.sh.XXXXXXXXXXX")

__crt__status_dir=$(mktemp -d "${TMPDIR:-/tmp}/concurrent.lib.sh.XXXXXXXXXXX")

ultimately generates a .../T//concurrent... which is odd, but I don't think is the problem.

Interestingly, I can login to a different user account, and the demo file works, log back in to the original and still have the problem.

[jacoscaz]

I've just stumbled into this, apparently at random. I'm 99.9% sure I have not touched my script, which uses concurrent behind the scenes, but it suddenly broke.

[jacoscaz]

Just in case someone else stumbles into this, in my case this was due to something else having linked a recent version of GNU sed into my $PATH, overriding Mac OS' own version.