From: brian m. carlson Date: Mon, 24 Oct 2022 00:28:49 GMT Subject: Re: waitpid errors with shell aliases Message-ID: In-Reply-To: On 2022-10-21 at 09:26:11, shubham sharma wrote: > Hi, > > I am using git shell aliases in config and was facing some weird > error. The error is not reproducible in all runs and occurs randomly > between runs...consider the minimal config(alias section) below for > usage idea: > > [alias] > A = "!f(){ \ > ( \ > // implementation > git \"$1\"; \ > ) 250 }; f" > B = "!f(){ \ > ssh ; \ > }; f" > C= "!f(){ \ > git A B; \ > }; f" > > when firing "git C" from shell,in some cases(not deterministically reproducible) > i observed weird waitpid errors of the type : > > error: waitpid for f(){ ssh ; }; f > failed: No child processes > fatal: while expanding alias 'B': 'f(){ ssh ; > }; f': No child processes > error: waitpid for f(){ (//implementation; git "$1"; )250 }; f failed: No child processes > fatal: while expanding alias 'A': 'f(){ (//implementation; git > "$1"; )250 error: waitpid for f(){ git A B; }; f failed: No child processes > fatal: while expanding alias 'C': 'f(){ git A B; }; f': No > child processes > > can anyone please help as to what could possibly be the reason for this? Could you tell us what OS and version of Git you're running, and what shell /bin/sh is? I could imagine that there might be some weirdness on Windows with the shell, but I would find an ECHILD to be surprising on Unix. -- brian m. carlson (he/him or they/them) Toronto, Ontario, CA